All of lore.kernel.org
 help / color / mirror / Atom feed
From: tangchen <tangchen@cn.fujitsu.com>
To: qemu-devel@nongnu.org, imammedo@redhat.com, mst@redhat.com,
	pbonzini@redhat.com
Cc: hutao@cn.fujitsu.com, isimatu.yasuaki@jp.fujitsu.com,
	zhugh.fnst@cn.fujitsu.com, tangchen@cn.fujitsu.com
Subject: Re: [Qemu-devel] [RFC PATCH v1 0/4] Handle memory hotplug errors from guest OS.
Date: Wed, 3 Sep 2014 17:05:38 +0800	[thread overview]
Message-ID: <5406D9E2.5080807@cn.fujitsu.com> (raw)
In-Reply-To: <53FD9362.8090404@cn.fujitsu.com>

Hi,

Would anyone help to review this patch-set ?
I'm not quit sure if this is a suitable way solve this problem.

Thanks.


On 08/27/2014 04:14 PM, tangchen wrote:
>
> Forgot to mention, this patch-set is based on the following patch-set:
>
> [RESEND PATCH v3 0/8] QEmu memory hot unplug support.
> https://www.mail-archive.com/qemu-devel@nongnu.org/msg253018.html
>
> Thanks.
>
> On 08/27/2014 04:09 PM, Tang Chen wrote:
>> When doing memory hotplug, QEmu is not aware of guest OS error when 
>> hotplugging
>> memory devices. Even if guest OS failed to hot-add memory, the pc-dimm
>> device will be added to QEmu. Even if guest OS failed to hot-remove 
>> memory,
>> QEmu will remove the pc-dimm device.
>>
>> An example is: for a Linux guest, the Linux kernel limited that the 
>> size of
>> hot-added memory should be mutiple of memory section (128MB by default).
>> If we add 130MB memory, the Linux kernel won't add it. We are not able
>> to handle the size check in QEmu commmand line because different OS may
>> have different limits.
>>
>> And also, QEmu outputs nothing but guest OS failed to hot-add memory 
>> will
>> confuse users. We should at least report an error.
>>
>> So, we should report the error to users, and cancel the memory hotplug
>> progress in QEmu.
>>
>> QEmu thread sends a SCI to guest OS and return immediately. The vcpu 
>> thread
>> will emulate ACPI hardware operations. So this patch-set introduces a 
>> wait
>> condition variable to synchronize these two threads.
>>
>> Tang Chen (4):
>>    Use macro to define ACPI notification event.
>>    Add event handling for memory device insertion.
>>    Introduce wait condition to catch guest OS memory hotplug error.
>>    Handle memory hotplug error from guest OS in QEmu.
>>
>>   hw/acpi/memory_hotplug.c | 146 
>> +++++++++++++++++++++++++++++++++++++++++++++--
>>   include/hw/acpi/acpi.h   |  15 ++++-
>>   2 files changed, 153 insertions(+), 8 deletions(-)
>>
>
> .
>

      reply	other threads:[~2014-09-03  9:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-27  8:09 [Qemu-devel] [RFC PATCH v1 0/4] Handle memory hotplug errors from guest OS Tang Chen
2014-08-27  8:09 ` [Qemu-devel] [RFC PATCH v1 1/4] Use macro to define ACPI notification event Tang Chen
2014-08-27  8:09 ` [Qemu-devel] [RFC PATCH v1 2/4] Add event handling for memory device insertion Tang Chen
2014-08-27  8:09 ` [Qemu-devel] [RFC PATCH v1 3/4] Introduce wait condition to catch guest OS memory hotplug error Tang Chen
2014-08-27  8:09 ` [Qemu-devel] [RFC PATCH v1 4/4] Handle memory hotplug error from guest OS in QEmu Tang Chen
2014-08-27  8:14 ` [Qemu-devel] [RFC PATCH v1 0/4] Handle memory hotplug errors from guest OS tangchen
2014-09-03  9:05   ` tangchen [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=5406D9E2.5080807@cn.fujitsu.com \
    --to=tangchen@cn.fujitsu.com \
    --cc=hutao@cn.fujitsu.com \
    --cc=imammedo@redhat.com \
    --cc=isimatu.yasuaki@jp.fujitsu.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=zhugh.fnst@cn.fujitsu.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 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.