From: "Michael S. Tsirkin" <mst@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: imammedo@redhat.com, qemu-devel@nongnu.org, ehabkost@redhat.com,
afaerber@suse.de
Subject: Re: [Qemu-devel] [for-2.1 PATCH v2 0/2] i386/acpi-build: support hotplug of VCPU with APIC ID 0xFF
Date: Mon, 17 Mar 2014 18:18:53 +0200 [thread overview]
Message-ID: <20140317161853.GB4785@redhat.com> (raw)
In-Reply-To: <1395072317-15679-1-git-send-email-lersek@redhat.com>
On Mon, Mar 17, 2014 at 05:05:15PM +0100, Laszlo Ersek wrote:
> New in v2:
> - simplify patch 2/2 by keeping the "acpi_cpus" local variable, only
> fixing up its type, and changing its initialization.
Applied, thanks!
> The current SSDT generator doesn't support hotplug of the VCPU with APIC
> ID 0xFF; supply that functionality.
>
> The series depends on Eduardo's
>
> [Qemu-devel] [PATCH v4 0/7] pc: Ensure APIC ID limits before aborting
> or corrupting memory
>
> Regression tested v1 with 4 VCPUs. Iasl disassembly of the SSDT remains
> identical (modulo length / checksum).
>
> Laszlo Ersek (2):
> i386/acpi-build: allow more than 255 elements in CPON
> i386/acpi-build: support hotplug of VCPU with APIC ID 0xFF
>
> hw/i386/acpi-build.c | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> --
> 1.8.3.1
prev parent reply other threads:[~2014-03-17 16:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 16:05 [Qemu-devel] [for-2.1 PATCH v2 0/2] i386/acpi-build: support hotplug of VCPU with APIC ID 0xFF Laszlo Ersek
2014-03-17 16:05 ` [Qemu-devel] [for-2.1 PATCH v2 1/2] i386/acpi-build: allow more than 255 elements in CPON Laszlo Ersek
2014-03-17 16:05 ` [Qemu-devel] [for-2.1 PATCH v2 2/2] i386/acpi-build: support hotplug of VCPU with APIC ID 0xFF Laszlo Ersek
2014-03-18 14:03 ` Michael S. Tsirkin
2014-03-18 14:54 ` Eduardo Habkost
2014-03-18 17:47 ` Laszlo Ersek
2014-03-17 16:18 ` Michael S. Tsirkin [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=20140317161853.GB4785@redhat.com \
--to=mst@redhat.com \
--cc=afaerber@suse.de \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=lersek@redhat.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 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.