public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: "Yang, Sheng" <sheng.yang@intel.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: VMX: Move private memory slot position
Date: Sat, 13 Sep 2008 11:55:27 +0300	[thread overview]
Message-ID: <48CB7FFF.1020306@qumranet.com> (raw)
In-Reply-To: <48CB4935.5090505@qumranet.com>

Avi Kivity wrote:
> Yang, Sheng wrote:
>   
>> On Thursday 04 September 2008 11:30:20 Yang, Sheng wrote:
>>   
>>     
>>> From ebe4ea311305d2910dcdcff2510662da0dc2c742 Mon Sep 17 00:00:00 2001
>>> From: Sheng Yang <sheng.yang@intel.com>
>>> Date: Thu, 4 Sep 2008 03:11:48 +0800
>>> Subject: [PATCH] KVM: VMX: Move private memory slot position
>>>
>>> PCI device assignment would map guest MMIO spaces as separate slot, so it
>>> is possible that the device has more than 2 MMIO spaces and overwrite
>>> current private memslot.
>>>
>>> The patch move private memory slot to the top of userspace visible memory
>>> slots.
>>>
>>>     
>>>       
>> Avi, these two?
>>   
>>     
>
> Thanks, applied both.
>
> Note that kvm now exports the number of slots using KVM_CAP_NR_MEMSLOTS,
> so userspace could be made dynamic.
>   

Well, the kernel change causes the host to oops while booting Windows on
an i386 pae host.  No idea why.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


  reply	other threads:[~2008-09-13  8:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-04  3:30 [PATCH] KVM: VMX: Move private memory slot position Yang, Sheng
2008-09-11  9:26 ` Yang, Sheng
2008-09-13  5:01   ` Avi Kivity
2008-09-13  8:55     ` Avi Kivity [this message]
2008-10-13  9:17       ` Yang, Sheng
2008-10-16  8:26         ` Avi Kivity
2008-10-16  8:42           ` Sheng Yang
2008-10-19 11:02             ` Avi Kivity

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=48CB7FFF.1020306@qumranet.com \
    --to=avi@qumranet.com \
    --cc=kvm@vger.kernel.org \
    --cc=sheng.yang@intel.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