From: Paolo Bonzini <pbonzini@redhat.com>
To: liu ping fan <qemulist@gmail.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [PATCH v2 3/3] hpet: entitle more irq pins for hpet
Date: Tue, 27 Aug 2013 11:46:02 +0200 [thread overview]
Message-ID: <521C755A.70706@redhat.com> (raw)
In-Reply-To: <CAJnKYQkn4BNxhdV5xaq4h4jyM3j-PGng-nYpX_Cq8QPVNaPjvw@mail.gmail.com>
Il 27/08/2013 11:01, liu ping fan ha scritto:
> On Tue, Aug 27, 2013 at 4:45 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>> Il 27/08/2013 10:10, Liu Ping Fan ha scritto:
>>> On q35 machine, IRQ2/8 can be reserved for hpet timer 0/1. And pin 16~23
>>> of ioapic can be dynamically assigned to hpet as guest chooses.
>>
>> First of all, the backwards-compatible q35 machines should also use the
>> old value.
>>
> Sorry but could you tell me why even on q35, we can only use IRQ2 for hpet?
Because the versioned machine types are supposed not to change the guest
ABI. This sometime requires bug-compatibility; for example, this
register is part of the guest ABI.
>> Second, the HPET should _not_ know the machine types. You need to add a
>> qdev property as I suggested in my reply to v1. The default value
>> should be 0xFF0104. Then you can add the compatibility value in
>> hw/i386/pc_piix.c and hw/i386/pc_q35.c.
>>
> So export the hpet's property at board-level?
Yes, the compat property mechanism can be used for this.
Paolo
> Regards,
> Pingfan
>>> ---
>>> hw/timer/hpet.c | 14 ++++++++++++--
>>> 1 file changed, 12 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/hw/timer/hpet.c b/hw/timer/hpet.c
>>> index 1139448..92cd4fa 100644
>>> --- a/hw/timer/hpet.c
>>> +++ b/hw/timer/hpet.c
>>> @@ -25,6 +25,7 @@
>>> */
>>>
>>> #include "hw/hw.h"
>>> +#include "hw/boards.h"
>>> #include "hw/i386/pc.h"
>>> #include "ui/console.h"
>>> #include "qemu/timer.h"
>>> @@ -42,6 +43,11 @@
>>>
>>> #define HPET_MSI_SUPPORT 0
>>>
>>> +/* only IRQ2 allowed for pc-1.6 and former */
>>> +#define HPET_TN_INT_CAP_PC (0x4ULL << 32)
>>> +/* Hpet can use non-legacy IRQ16~23, and an IRQ2 ,IRQ8 */
>>> +#define HPET_TN_INT_CAP_Q35 (0xff0104ULL << 32)
>>> +
>>> #define TYPE_HPET "hpet"
>>> #define HPET(obj) OBJECT_CHECK(HPETState, (obj), TYPE_HPET)
>>>
>>> @@ -663,8 +669,12 @@ static void hpet_reset(DeviceState *d)
>>> if (s->flags & (1 << HPET_MSI_SUPPORT)) {
>>> timer->config |= HPET_TN_FSB_CAP;
>>> }
>>> - /* advertise availability of ioapic inti2 */
>>> - timer->config |= 0x00000004ULL << 32;
>>> + /* advertise availability of ioapic int */
>>> + if (qemu_check_machine("pc-q35")) {
>>> + timer->config |= HPET_TN_INT_CAP_Q35;
>>> + } else {
>>> + timer->config |= HPET_TN_INT_CAP_PC;
>>> + }
>>> timer->period = 0ULL;
>>> timer->wrap_flag = 0;
>>> }
>>>
>>
prev parent reply other threads:[~2013-08-27 9:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 8:10 [Qemu-devel] [PATCH v2 1/3] hpet: inverse polarity when pin above ISA_NUM_IRQS Liu Ping Fan
2013-08-27 8:10 ` [Qemu-devel] [PATCH v2 2/3] vl: add func to check the machine type Liu Ping Fan
2013-08-27 8:10 ` [Qemu-devel] [PATCH v2 3/3] hpet: entitle more irq pins for hpet Liu Ping Fan
2013-08-27 8:45 ` Paolo Bonzini
2013-08-27 9:01 ` liu ping fan
2013-08-27 9:46 ` Paolo Bonzini [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=521C755A.70706@redhat.com \
--to=pbonzini@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
--cc=qemulist@gmail.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).