From: "Andreas Färber" <afaerber@suse.de>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 4/5] pc: add 1.6 compat type
Date: Thu, 30 May 2013 17:55:35 +0200 [thread overview]
Message-ID: <51A77677.4080207@suse.de> (raw)
In-Reply-To: <1369911913-10934-5-git-send-email-mst@redhat.com>
Am 30.05.2013 13:07, schrieb Michael S. Tsirkin:
> Identical to 1.5 ATM, but changes will accumulate.
>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
You did notice that Eduardo had a similar patch yesterday or so?
Yours does not handle q35 by comparison.
> ---
> hw/i386/pc_piix.c | 13 ++++++++++++-
> 1 file changed, 12 insertions(+), 1 deletion(-)
>
> diff --git a/hw/i386/pc_piix.c b/hw/i386/pc_piix.c
> index eaff0b6..2717d83 100644
> --- a/hw/i386/pc_piix.c
> +++ b/hw/i386/pc_piix.c
> @@ -57,6 +57,7 @@ static const int ide_iobase2[MAX_IDE_BUS] = { 0x3f6, 0x376 };
> static const int ide_irq[MAX_IDE_BUS] = { 14, 15 };
>
> static bool has_pvpanic = true;
> +static bool has_pci_info = true;
I don't see this used here, and it's replaced in next patch.
Andreas
>
> /* PC hardware initialisation */
> static void pc_init1(MemoryRegion *system_memory,
> @@ -340,9 +341,19 @@ static void pc_xen_hvm_init(QEMUMachineInitArgs *args)
> }
> #endif
>
> +static QEMUMachine pc_i440fx_machine_v1_6 = {
> + .name = "pc-i440fx-1.6",
> + .alias = "pc",
> + .desc = "Standard PC (i440FX + PIIX, 1996)",
> + .init = pc_init_pci,
> + .hot_add_cpu = pc_hot_add_cpu,
> + .max_cpus = 255,
> + .is_default = 1,
> + DEFAULT_MACHINE_OPTIONS,
> +};
> +
> static QEMUMachine pc_i440fx_machine_v1_5 = {
> .name = "pc-i440fx-1.5",
> - .alias = "pc",
> .desc = "Standard PC (i440FX + PIIX, 1996)",
> .init = pc_init_pci,
> .hot_add_cpu = pc_hot_add_cpu,
>
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-05-30 15:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 11:07 [Qemu-devel] [PATCH v2 0/5] pc: pass pci window data to guests Michael S. Tsirkin
2013-05-30 11:07 ` [Qemu-devel] [PATCH v2 1/5] range: add Range structure Michael S. Tsirkin
2013-05-31 2:41 ` Hu Tao
2013-05-30 11:07 ` [Qemu-devel] [PATCH v2 2/5] pci: store PCI hole ranges in guestinfo structure Michael S. Tsirkin
2013-05-30 12:16 ` Gerd Hoffmann
2013-05-30 12:19 ` Michael S. Tsirkin
2013-05-30 12:32 ` Gerd Hoffmann
2013-05-30 12:55 ` Michael S. Tsirkin
2013-05-31 5:43 ` Gerd Hoffmann
2013-05-30 12:25 ` Laszlo Ersek
2013-05-30 12:45 ` Michael S. Tsirkin
2013-05-31 3:26 ` Hu Tao
2013-05-30 11:07 ` [Qemu-devel] [PATCH v2 3/5] pc: pass PCI hole ranges to Guests Michael S. Tsirkin
2013-05-30 11:07 ` [Qemu-devel] [PATCH v2 4/5] pc: add 1.6 compat type Michael S. Tsirkin
2013-05-30 15:55 ` Andreas Färber [this message]
2013-05-30 17:40 ` Michael S. Tsirkin
2013-05-30 11:07 ` [Qemu-devel] [PATCH v2 5/5] pc: pci-info add compat support Michael S. Tsirkin
2013-05-30 16:32 ` Laszlo Ersek
2013-05-30 17:39 ` Michael S. Tsirkin
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=51A77677.4080207@suse.de \
--to=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=ehabkost@redhat.com \
--cc=mst@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).