qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Anthony Liguori" <anthony@codemonkey.ws>,
	"Jan Kiszka" <jan.kiszka@siemens.com>,
	qemu-devel@nongnu.org, "liu ping fan" <qemulist@gmail.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH v5 2/5] hpet: entitle more irq pins for hpet
Date: Wed, 09 Oct 2013 09:41:29 +0200	[thread overview]
Message-ID: <525508A9.2030004@redhat.com> (raw)
In-Reply-To: <20131009072433.GB30623@redhat.com>

Il 09/10/2013 09:24, Michael S. Tsirkin ha scritto:
>> > Sorry, out of office for a long time, and did not keep up with this
>> > thread in time.
>> > When letting the caller set the intcap, we should consider the
>> > compatibility of q35. For pc-q35-1.7 or later, the caller should set
>> > the property, otherwise not.
> Set it always - just set it to a compatible value for 1.6.
> 

So you're suggesting skipping the mechanism we have for compatibility
properties, and instead using a global variable or something like that?

Paolo

  reply	other threads:[~2013-10-09  7:41 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-12  3:25 [Qemu-devel] [PATCH v5 0/5] bugs fix for hpet Liu Ping Fan
2013-09-12  3:25 ` [Qemu-devel] [PATCH v5 1/5] hpet: inverse polarity when pin above ISA_NUM_IRQS Liu Ping Fan
2013-09-28 19:52   ` Michael S. Tsirkin
2013-09-29  3:25     ` liu ping fan
2013-09-29  4:20       ` Michael S. Tsirkin
2013-09-30  8:04         ` liu ping fan
2013-09-12  3:25 ` [Qemu-devel] [PATCH v5 2/5] hpet: entitle more irq pins for hpet Liu Ping Fan
2013-09-28 19:56   ` Michael S. Tsirkin
2013-09-29  3:49     ` liu ping fan
2013-09-29  4:15       ` Michael S. Tsirkin
2013-09-30  8:02         ` liu ping fan
2013-09-30  9:06           ` Michael S. Tsirkin
2013-09-30  9:06             ` Paolo Bonzini
2013-09-30  9:30               ` Michael S. Tsirkin
2013-09-30 15:48                 ` Paolo Bonzini
2013-09-30 15:58                   ` Michael S. Tsirkin
2013-10-09  3:27                     ` liu ping fan
2013-10-09  7:24                       ` Michael S. Tsirkin
2013-10-09  7:41                         ` Paolo Bonzini [this message]
2013-10-09  8:01                           ` Michael S. Tsirkin
2013-10-09  8:41                             ` Paolo Bonzini
2013-09-12  3:25 ` [Qemu-devel] [PATCH v5 3/5] PC: use qdev_xx to create hpet instead of sysbus_create_xx Liu Ping Fan
2013-09-12  3:25 ` [Qemu-devel] [PATCH v5 4/5] PC: differentiate hpet's interrupt capability on piix and q35 Liu Ping Fan
2013-09-12  3:25 ` [Qemu-devel] [PATCH v5 5/5] PC-1.6: add compatibility for hpet intcap on pc-q35-1.6 Liu Ping Fan
2013-09-12  6:29 ` [Qemu-devel] [PATCH v5 0/5] bugs fix for hpet Paolo Bonzini
2013-09-12  7:49   ` liu ping fan
2013-09-25  6:27 ` liu ping fan
2013-09-25 15:59   ` Paolo Bonzini
2013-09-26 15:45     ` Mike Day
2013-09-26 15:48     ` Mike Day

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=525508A9.2030004@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=afaerber@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=jan.kiszka@siemens.com \
    --cc=mst@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemulist@gmail.com \
    --cc=stefanha@redhat.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 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).