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 1/2] hpet: entitle more irq pins for hpet
Date: Mon, 26 Aug 2013 09:59:56 +0200 [thread overview]
Message-ID: <521B0AFC.7010603@redhat.com> (raw)
In-Reply-To: <CAJnKYQnX3iey169sbMoGN9NBUL+EAyGdNkfT5vdmTvucfRkLtA@mail.gmail.com>
Il 26/08/2013 04:53, liu ping fan ha scritto:
> On Sun, Aug 25, 2013 at 2:45 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>> Il 25/08/2013 04:16, Liu Ping Fan ha scritto:
>>> On PC, 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.
>>>
>>> Signed-off-by: Liu Ping Fan <pingfank@linux.vnet.ibm.com>
>>> ---
>>> hw/timer/hpet.c | 6 ++++--
>>> 1 file changed, 4 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/hw/timer/hpet.c b/hw/timer/hpet.c
>>> index 648b383..cd95d39 100644
>>> --- a/hw/timer/hpet.c
>>> +++ b/hw/timer/hpet.c
>>> @@ -41,6 +41,8 @@
>>> #endif
>>>
>>> #define HPET_MSI_SUPPORT 0
>>> +/* Hpet can use non-legacy IRQ16~23, and an IRQ2 ,IRQ8 */
>>> +#define HPET_TN_INT_CAP (0xff0104ULL << 32)
>>>
>>> #define TYPE_HPET "hpet"
>>> #define HPET(obj) OBJECT_CHECK(HPETState, (obj), TYPE_HPET)
>>> @@ -653,8 +655,8 @@ 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 */
>>> + timer->config |= HPET_TN_INT_CAP;
>>> timer->period = 0ULL;
>>> timer->wrap_flag = 0;
>>> }
>>>
>>
>> These high 32-bits of timer->config need to be a property of the HPET
>> devices, so that the old value (4) is used when running with old machine
>
> Sorry, but I had included old value (4) in macro HPET_TN_INT_CAP.
No, *only* GSI 2 must be available on old machine types (pc-1.6 and older).
Paolo
next prev parent reply other threads:[~2013-08-26 8:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-25 2:16 [Qemu-devel] [PATCH 1/2] hpet: entitle more irq pins for hpet Liu Ping Fan
2013-08-25 2:16 ` [Qemu-devel] [PATCH 2/2] hpet: inverse polarity when pin above ISA_NUM_IRQS Liu Ping Fan
2013-08-25 6:44 ` Paolo Bonzini
2013-08-26 2:49 ` liu ping fan
2013-08-25 6:45 ` [Qemu-devel] [PATCH 1/2] hpet: entitle more irq pins for hpet Paolo Bonzini
2013-08-26 2:53 ` liu ping fan
2013-08-26 7:59 ` Paolo Bonzini [this message]
2013-08-26 8:30 ` liu ping fan
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=521B0AFC.7010603@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).