From: Jan Kiszka <jan.kiszka@siemens.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [RFC][PATCH] x86: Optional segment type and limit checks - v2
Date: Tue, 15 Jul 2008 17:43:40 +0200 [thread overview]
Message-ID: <487CC5AC.2070900@siemens.com> (raw)
In-Reply-To: <20080714110507.GD29536@redhat.com>
Daniel P. Berrange wrote:
> On Mon, Jul 14, 2008 at 12:34:48PM +0200, Jan Kiszka wrote:
>> This is the second version of my segment type and register check. It
>> reduces the impact on the translator code significantly, and it also
>> fixes a bug of the "size" helper variant in the previous version.
>>
>> The idea of this patch is to generate calls to a check helper only in
>> case the user requested this support via "-seg-checks". This feature
>> remains off by default as most x86 OSes do not care about protection via
>> segmentation anymore (and it was even removed from 64-bit modes by the
>> CPU vendors).
>
> Two current users of protection via segmentation I know of
>
> - 32-bit linux with the ExecShield capability will still use segmentation
> to split the address space into executable vs non-executable regions, if
> the CPU doesn't have NX bit support.
> - 32-bit Xen uses segmentation for protecting the hypervisor.
Ah, good to be reminded that we are not alone with our segmented OS here. ;)
That makes me realize that my patch lacks range checks for code
segments. I think I left it out as it is not that trivial...
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2008-07-15 15:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-09 12:12 [Qemu-devel] [RFC][PATCH] x86: Optional segment type and limit checks Jan Kiszka
2008-07-14 10:34 ` [Qemu-devel] [RFC][PATCH] x86: Optional segment type and limit checks - v2 Jan Kiszka
2008-07-14 10:55 ` Jamie Lokier
2008-07-14 11:11 ` Paul Brook
2008-07-14 14:02 ` Jamie Lokier
2008-07-14 17:50 ` Kevin O'Connor
2008-07-14 18:51 ` Jamie Lokier
2008-07-15 15:48 ` [Qemu-devel] " Jan Kiszka
2008-07-15 16:12 ` Jamie Lokier
2008-07-16 1:20 ` Kevin O'Connor
2008-07-16 2:43 ` Kevin O'Connor
2008-07-14 11:05 ` [Qemu-devel] " Daniel P. Berrange
2008-07-15 15:43 ` Jan Kiszka [this message]
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=487CC5AC.2070900@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.