From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: Markus Armbruster <armbru@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
qemu-devel <qemu-devel@nongnu.org>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/3] pc: Fix disabling of vapic for compat PC models
Date: Tue, 02 Sep 2014 10:11:25 -0500 [thread overview]
Message-ID: <20140902151125.16792.32360@loki> (raw)
In-Reply-To: <87a97rnlfb.fsf@blackfin.pond.sub.org>
Quoting Markus Armbruster (2014-07-30 06:19:36)
> Paolo Bonzini <pbonzini@redhat.com> writes:
>
> > Il 30/07/2014 10:57, Michael S. Tsirkin ha scritto:
> >> On Wed, Jul 30, 2014 at 09:01:59AM +0200, Jan Kiszka wrote:
> >>> We used to be able to address both the QEMU and the KVM APIC via "apic".
> >>> This doesn't work anymore. So we need to use their parent class to turn
> >>> off the vapic on machines that should not expose them.
> >>>
> >>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> >>
> >>
> >>
> >> OK so this is intended for 2.2?
>
> If yes, we should cc: qemu-stable.
Ping for stable 2.1.1, freeze is on Wednesday
>
> >> In that case, how about creating a macro with type name,
> >> and using that? This way things don't break if we rename
> >> something again.
> >
> > Don't we have warnings for that now?
>
> Warnings don't help much in cases like this: "apic" still exists and has
> the property, it's just not the device we want. Macros aren't
> foolproof, either.
>
> >>> ---
> >>> hw/i386/pc_piix.c | 2 +-
> >>> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>>
> >>> diff --git a/hw/i386/pc_piix.c b/hw/i386/pc_piix.c
> >>> index 9694f88..73ba77d 100644
> >>> --- a/hw/i386/pc_piix.c
> >>> +++ b/hw/i386/pc_piix.c
> >>> @@ -645,7 +645,7 @@ static QEMUMachine pc_machine_v1_1 = {
> >>> .property = "class",\
> >>> .value = stringify(PCI_CLASS_MEMORY_RAM),\
> >>> },{\
> >>> - .driver = "apic",\
> >>> + .driver = "apic-common",\
> >>> .property = "vapic",\
> >>> .value = "off",\
> >>> },{\
> >>> --
> >>> 1.8.1.1.298.ge7eed54
>
> You could use TYPE_APIC_COMMON here. Including
> "hw/i386/apic_internal.h" for it would be not so nice, though.
next prev parent reply other threads:[~2014-09-02 15:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 7:01 [Qemu-devel] [PATCH 0/3] pc: Small fixes for Intel HDA config space and PC_COMPAT_1_0 Jan Kiszka
2014-07-30 7:01 ` [Qemu-devel] [PATCH 1/3] pc: Fix disabling of vapic for compat PC models Jan Kiszka
2014-07-30 8:57 ` Michael S. Tsirkin
2014-07-30 9:11 ` Paolo Bonzini
2014-07-30 11:19 ` Markus Armbruster
2014-09-02 15:11 ` Michael Roth [this message]
2014-10-02 7:27 ` Jan Kiszka
2014-10-02 8:03 ` Michael S. Tsirkin
2014-10-02 8:05 ` Jan Kiszka
2014-10-02 8:17 ` Michael S. Tsirkin
2014-07-30 7:02 ` [Qemu-devel] [PATCH 2/3] pc: Create 2.2 machine type Jan Kiszka
2014-07-30 8:41 ` Alex Bligh
2014-07-30 8:44 ` Jan Kiszka
2014-07-30 7:02 ` [Qemu-devel] [PATCH 3/3] hw/audio/intel-hda: Fix MSI capability address Jan Kiszka
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=20140902151125.16792.32360@loki \
--to=mdroth@linux.vnet.ibm.com \
--cc=armbru@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=mst@redhat.com \
--cc=pbonzini@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).