From: Avi Kivity <avi@redhat.com>
To: "Kevin O'Connor" <kevin@koconnor.net>
Cc: Mohammed Gamal <m.gamal005@gmail.com>,
mtosatti@redhat.com, kvm@vger.kernel.org
Subject: Re: [RFC PATCH v3 0/3] Add segment limit checks to emulator
Date: Mon, 26 Jul 2010 14:47:14 +0300 [thread overview]
Message-ID: <4C4D75C2.4000404@redhat.com> (raw)
In-Reply-To: <20100725162328.GA18995@morn.localdomain>
On 07/25/2010 07:23 PM, Kevin O'Connor wrote:
> On Sun, Jul 25, 2010 at 11:54:20AM +0300, Avi Kivity wrote:
>> On 07/24/2010 06:45 PM, Kevin O'Connor wrote:
>>> On Mon, Jul 12, 2010 at 04:13:06PM +0300, Avi Kivity wrote:
>>>> Does SeaBIOS use big real mode now?
>>> SeaBIOS calls option roms in big real mode. This is required by the
>>> relevant specs.
>> Can you provide a pointer?
> See the PMM spec section 2.2 and section 3.2.4. (Sadly, I can't find
> a link to the PMM spec on the web anymore - hopefully you have a
> copy.) Also see the PCI Firmware Specification v3.0 - section
> 5.2.1.9.
Unfortunately, I don't have a copy.
> The specs don't require any code addresses to be>64K, but it does
> require data access over 64K. I doubt there are many systems that use
> a code address>64K, because an interrupt in big real mode still only
> stores a 16bit return address - thus an irq (or nmi) in that mode will
> basically cause a crash.
Ok. Flat 4G segments happen to accidentally work in kvm-intel, and we
can keep it working.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-07-26 11:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-11 22:56 [RFC PATCH v3 0/3] Add segment limit checks to emulator Mohammed Gamal
2010-07-11 22:56 ` [RFC PATCH v3 1/3] Add helper methods to get segment limits Mohammed Gamal
2010-07-11 22:56 ` [RFC PATCH v3 2/3] x86 emulator: Add segment limit checking helpers Mohammed Gamal
2010-07-11 22:56 ` [RFC PATCH v3 3/3] x86 emulator: Add segment limit checks to emulator functions Mohammed Gamal
2010-07-12 6:26 ` [RFC PATCH v3 0/3] Add segment limit checks to emulator Avi Kivity
2010-07-12 12:36 ` Mohammed Gamal
2010-07-12 13:13 ` Avi Kivity
[not found] ` <AANLkTimHvpE05chocuoQnY0ydOMchMcIInu9QX5F_pV4@mail.gmail.com>
2010-07-12 13:51 ` Avi Kivity
2010-07-12 14:41 ` Gleb Natapov
2010-07-12 14:49 ` Avi Kivity
2010-07-24 15:45 ` Kevin O'Connor
2010-07-24 16:16 ` Kevin O'Connor
2010-07-25 8:55 ` Avi Kivity
2010-07-25 16:42 ` Kevin O'Connor
2010-07-25 17:19 ` Kevin O'Connor
2010-07-25 18:34 ` Avi Kivity
2010-07-25 18:55 ` Kevin O'Connor
2010-07-25 8:54 ` Avi Kivity
2010-07-25 16:23 ` Kevin O'Connor
2010-07-26 11:47 ` Avi Kivity [this message]
2010-07-26 17:47 ` Stefan Hajnoczi
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=4C4D75C2.4000404@redhat.com \
--to=avi@redhat.com \
--cc=kevin@koconnor.net \
--cc=kvm@vger.kernel.org \
--cc=m.gamal005@gmail.com \
--cc=mtosatti@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