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
On Mon, Jul 26, 2010 at 12:47 PM, Avi Kivity a...@redhat.com wrote:
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
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 transition16big function in
On 07/24/2010 07:16 PM, Kevin O'Connor wrote:
On Sat, Jul 24, 2010 at 11:45:22AM -0400, 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.
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.
On Sun, Jul 25, 2010 at 11:55:47AM +0300, Avi Kivity wrote:
On 07/24/2010 07:16 PM, Kevin O'Connor wrote:
On Sat, Jul 24, 2010 at 11:45:22AM -0400, 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
On Sun, Jul 25, 2010 at 12:42:46PM -0400, Kevin O'Connor wrote:
On Sun, Jul 25, 2010 at 11:55:47AM +0300, Avi Kivity wrote:
What conditions are needed to trigger this path? This can't occur
under normal operation, since it will fail badly with kvm on Intel.
It's called on every boot.
On 07/25/2010 08:19 PM, Kevin O'Connor wrote:
On Sun, Jul 25, 2010 at 12:42:46PM -0400, Kevin O'Connor wrote:
On Sun, Jul 25, 2010 at 11:55:47AM +0300, Avi Kivity wrote:
What conditions are needed to trigger this path? This can't occur
under normal operation, since it will fail badly with
On Sun, Jul 25, 2010 at 09:34:38PM +0300, Avi Kivity wrote:
On 07/25/2010 08:19 PM, Kevin O'Connor wrote:
Only the ljmpw is in big real mode with a code address64K - the
Disable protected mode code is technically in 16bit protected mode.
I'm not sure if that helps explain why it works.
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.
See the transition16big function in src/romlayout.S. It briefly jumps
to an address at 0xffxxx during the
On Sat, Jul 24, 2010 at 11:45:22AM -0400, 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.
See the transition16big function in
On 07/12/2010 01:56 AM, Mohammed Gamal wrote:
fter some conversation with Avi concerning why unreal mode has been seen to work
with KVM on Intel. It clears out the scenario is caused as follows:
- guest enters big real mode
- kvm squashes limit to 64k-1
- guest executes instructions with offset
On Mon, Jul 12, 2010 at 9:26 AM, Avi Kivity a...@redhat.com wrote:
On 07/12/2010 01:56 AM, Mohammed Gamal wrote:
fter some conversation with Avi concerning why unreal mode has been seen
to work
with KVM on Intel. It clears out the scenario is caused as follows:
- guest enters big real mode
On 07/12/2010 03:36 PM, Mohammed Gamal wrote:
On Mon, Jul 12, 2010 at 9:26 AM, Avi Kivitya...@redhat.com wrote:
On 07/12/2010 01:56 AM, Mohammed Gamal wrote:
fter some conversation with Avi concerning why unreal mode has been seen
to work
with KVM on Intel. It clears out the
On 07/12/2010 04:39 PM, Mohammed Gamal wrote:
What happens is that guests are switched to big real mode so either
gPXE and SeaBIOS need to be modified to work with the way KVM handles
segment limits when switching to real mode, but that'd be only a
temporary solution. The other - and better
On Mon, Jul 12, 2010 at 04:51:10PM +0300, Avi Kivity wrote:
On 07/12/2010 04:39 PM, Mohammed Gamal wrote:
What happens is that guests are switched to big real mode so either
gPXE and SeaBIOS need to be modified to work with the way KVM handles
segment limits when switching to real mode, but
On 07/12/2010 05:41 PM, Gleb Natapov wrote:
A good way to do this is to add a segment variable to 'struct
operand', and doing all the base adjustment at the end (instead of
up front as we do now). That means we'll have the minimum number of
places to add checks to.
-read_emulated(),
fter some conversation with Avi concerning why unreal mode has been seen to work
with KVM on Intel. It clears out the scenario is caused as follows:
- guest enters big real mode
- kvm squashes limit to 64k-1
- guest executes instructions with offset 64k
- cpu issues #GP due to limit violation
-
18 matches
Mail list logo
