qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC][PATCH] x86: Optional segment type and limit checks - v2
Date: Mon, 14 Jul 2008 12:11:49 +0100	[thread overview]
Message-ID: <200807141211.49825.paul@codesourcery.com> (raw)
In-Reply-To: <20080714105531.GB2381@shareable.org>

> Some 32-bit guests effectively disable segment range calculations
> checks by setting the maximum limit and zero offset.  Apparently, this
> is faster on some real CPUs too.
>
> Could type checking be done at translation time, including the segment
> types in the translation cache key?

Maybe. If we have a spare hflags bit you could probably use that to indicate 
whether segment limit checks are needed.

> For guests like older Linux, with zero base and non-maximum limit in
> user mode, could limit checking be done by the MMU TLB instead?

Not really. The only resonable way to do this would be to use a very large 
virtual address space, with the high bits being the segment descriptor.  This 
might work for 32-bit targets on 64-bit hosts, but even then it's liable to 
be more pain than it's worth.

Paul

  reply	other threads:[~2008-07-14 11:12 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 [this message]
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     ` [Qemu-devel] " Jan Kiszka

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=200807141211.49825.paul@codesourcery.com \
    --to=paul@codesourcery.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 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 NNTP newsgroup(s).