From: Paolo Bonzini <bonzini@gnu.org>
To: Richard Henderson <rth@redhat.com>,
gcc-patches@gcc.gnu.org, Avi Kivity <avi.kivity@gmail.com>
Subject: Re: [PATCH 5/9] i386: Add address spaces for fs/gs segments
Date: Fri, 16 Oct 2015 15:29:00 -0000 [thread overview]
Message-ID: <5621179F.5070303@gnu.org> (raw)
In-Reply-To: <1444280375-20866-6-git-send-email-rth@redhat.com>
On 08/10/2015 06:59, Richard Henderson wrote:
> +/* Address space support.
> +
> + This is not "far pointers" in the 16-bit sense, but an easy way
> + to use %fs and %gs segment prefixes. Therefore:
> +
> + (a) All address spaces have the same modes,
> + (b) All address spaces have the same addresss forms,
> + (c) While %fs and %gs are technically subsets of the generic
> + address space, they are probably not subsets of each other.
> + (d) Since we have no access to the segment base register values
> + without resorting to a system call, we cannot convert a
> + non-default address space to a default address space.
> + Therefore we do not claim %fs or %gs are subsets of generic.
rdfsbase and rdgsbase are potentially accessible to userspace too, so I
think %fs or %gs should be considered subsets of generic.
Paolo
> + Therefore, we need not override any of the address space hooks. */
next prev parent reply other threads:[~2015-10-16 15:28 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 5:00 [RFA 0/9] Address space support for x86 Richard Henderson
2015-10-08 5:00 ` [PATCH 4/9] i386: Disallow address spaces with string insns Richard Henderson
2015-10-08 5:00 ` [PATCH 5/9] i386: Add address spaces for fs/gs segments Richard Henderson
2015-10-16 15:29 ` Paolo Bonzini [this message]
2015-10-18 23:47 ` Richard Henderson
2015-10-08 5:00 ` [PATCH 9/9] Fix PR 66768 Richard Henderson
2015-10-08 5:17 ` Bin.Cheng
2015-10-08 9:55 ` Bernd Schmidt
2015-10-08 10:12 ` Bin.Cheng
2015-10-08 10:25 ` Richard Biener
2015-10-08 5:00 ` [PATCH 1/9] Change default of non-overlapping address space conversion Richard Henderson
2015-10-09 10:48 ` Bernd Schmidt
2015-10-08 5:00 ` [PATCH 7/9] i386: Add address space for tls Richard Henderson
2015-10-08 8:30 ` Florian Weimer
2015-10-08 5:00 ` [PATCH 2/9] Relax ADDR_SPACE_GENERIC_P checks for default address space hooks Richard Henderson
2015-10-08 10:10 ` Richard Biener
2015-10-08 5:00 ` [PATCH 3/9] i386: Handle address spaces in movabs patterns Richard Henderson
2015-10-08 5:00 ` [PATCH 8/9] Add TARGET_ADDR_SPACE_ZERO_ADDRESS_VALID Richard Henderson
2015-10-08 10:20 ` Richard Biener
2015-10-09 22:13 ` Richard Henderson
2015-10-12 10:10 ` Richard Biener
2015-10-12 23:27 ` Richard Henderson
2015-10-13 10:13 ` Richard Biener
2015-10-13 15:49 ` Jeff Law
2015-10-13 20:59 ` Richard Henderson
2015-10-14 9:19 ` Richard Biener
2015-10-14 9:22 ` Richard Biener
2015-10-14 21:20 ` Richard Henderson
2015-10-14 15:28 ` Jeff Law
2015-10-14 15:22 ` Jeff Law
2015-10-08 5:00 ` [PATCH 6/9] i386: Replace ix86_address_seg with addr_space_t Richard Henderson
2015-10-08 10:07 ` [RFA 0/9] Address space support for x86 Richard Biener
2015-10-09 22:13 ` Richard Henderson
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=5621179F.5070303@gnu.org \
--to=bonzini@gnu.org \
--cc=avi.kivity@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rth@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).