From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: jhb@FreeBSD.org
Cc: palves@redhat.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] Add support for the x86 XSAVE extended state on FreeBSD/x86.
Date: Sat, 21 Mar 2015 20:18:00 -0000 [thread overview]
Message-ID: <201503212018.t2LKI3jm000615@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <550DC328.40800@FreeBSD.org> (message from John Baldwin on Sat, 21 Mar 2015 15:14:48 -0400)
> Date: Sat, 21 Mar 2015 15:14:48 -0400
> From: John Baldwin <jhb@FreeBSD.org>
>
> >> + if (x86_xsave_len != 0)
> >> + {
> >> + switch (xcr0 & X86_XSTATE_ALL_MASK)
> >> + {
> >> + case X86_XSTATE_MPX_AVX512_MASK:
> >> + case X86_XSTATE_AVX512_MASK:
> >> + if (is64)
> >> + return tdesc_amd64_avx512;
> >> + else
> >> + return tdesc_i386_avx512;
> >> + case X86_XSTATE_MPX_MASK:
> >> + if (is64)
> >> + return tdesc_amd64_mpx;
> >> + else
> >> + return tdesc_i386_mpx;
> >> + case X86_XSTATE_AVX_MASK:
> >> + if (is64)
> >> + return tdesc_amd64_avx;
> >> + else
> >> + return tdesc_i386_avx;
> >> + default:
> >> + if (is64)
> >> + return tdesc_amd64;
> >> + else
> >> + return tdesc_i386;
> >> + }
> >
> > These xcr0 -> tdesc mappings need to appear in multiple places.
> > I wonder whether it'd make sense to put them in a single helper
> > function (in the fbsd tdep file) that takes "xcr0" and "is64" as
> > parameters, and returns the corresponding tdesc.
>
> There are a couple of options I've thought about for this. One
> has been to have a shared to_read_description implementation in
> an x86fbsd-nat.c (Linux uses a shared one in x86-linux-nat.c).
> However, these case statements are also not really FreeBSD (or BSD)
> specific. What if I added functions in amd64-tdep.c and i386-tdep.c
> that returned the correct target description for a given xcr0
> value? Something like:
>
> struct target_desc *
> i386_target_description(uint64_t xcr0)
> {
>
> /* i386 switch statement here */
> }
>
> That could be reused for the core read_description callback as
> well as the native ones. This could also be reused by other
> systems that grow XSAVE support in the future.
Probably a good idea. I'm working on XSAVE support in the OpenBSD
kernel, so I'll eventually need this as well.
I have no real objection to adding the ptrace-specific bits to the
generic BSD native code like your diff is doing. I'll probably try to
use the same interface for my OpenBSD implementation. I have one
concern about that code though. The _supply_xsave() and
_collect_xsave() functions don't accept a length, so they can't do any
bounds checking. Therefore, 'xstat_bv' as returned by the kernel must
be set correctly (i.e. not have bits sets that imply state beyond
x86_save_len is present. Does the FreeBSD kernel guarantee that?
Oh, and please rename x86_xsave_len into amd64bsd_xsave_len and
i386bsd_xsave_len to keep the "namesapce" clean.
next prev parent reply other threads:[~2015-03-21 20:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 14:50 John Baldwin
2015-03-18 20:00 ` Pedro Alves
2015-03-21 19:14 ` John Baldwin
2015-03-21 20:18 ` Mark Kettenis [this message]
2015-03-21 22:29 ` John Baldwin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201503212018.t2LKI3jm000615@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sourceware.org \
--cc=jhb@FreeBSD.org \
--cc=palves@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox