qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Michael Roth <mdroth@linux.vnet.ibm.com>,
	Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/3] pc: Fix disabling of vapic for compat PC models
Date: Thu, 2 Oct 2014 11:17:07 +0300	[thread overview]
Message-ID: <20141002081707.GC19369@redhat.com> (raw)
In-Reply-To: <542D0752.3090300@siemens.com>

On Thu, Oct 02, 2014 at 10:05:38AM +0200, Jan Kiszka wrote:
> On 2014-10-02 10:03, Michael S. Tsirkin wrote:
> > On Thu, Oct 02, 2014 at 09:27:41AM +0200, Jan Kiszka wrote:
> >> On 2014-09-02 17:11, Michael Roth wrote:
> >>> 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
> >>
> >> Lost track of this: was I supposed to provide anything different, or did
> >> this just fall under the table?
> >>
> >> Jan
> > 
> > Yes, I think Michael expected an ACK for stable.
> > Oh well.
> > Would you like me to apply as is, or to rework this to avoid duplication
> > of string names?
> 
> I don't mind, but I wouldn't refuse if you want to take care of the issue.
> 
> Jan

I've applied as-is for now, thanks.


I think the use of strings in compat machine types
is too fragile, we should have a header with
type names, and reuse it through macros, but
apic is not unique here.

> -- 
> Siemens AG, Corporate Technology, CT RTC ITP SES-DE
> Corporate Competence Center Embedded Linux

  reply	other threads:[~2014-10-02  8:13 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
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 [this message]
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=20141002081707.GC19369@redhat.com \
    --to=mst@redhat.com \
    --cc=armbru@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=mdroth@linux.vnet.ibm.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).