qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Wanpeng Li <liwp@linux.vnet.ibm.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] fix bug of isa_bus irq
Date: Mon, 12 Mar 2012 07:55:18 +0100	[thread overview]
Message-ID: <4F5D9DD6.4060806@web.de> (raw)
In-Reply-To: <20120312060850.GB31217@liwp@linux.vnet.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 2048 bytes --]

On 2012-03-12 07:08, Wanpeng Li wrote:
> On Sun, Mar 11, 2012 at 08:46:38AM +0100, Jan Kiszka wrote:
>> On 2012-03-11 08:04, Wanpeng Li wrote:
>>> ISA bus only use IRQ 0~15, so don't need to give an array qemu_irq 0~23, just
>>> array qemu_irq i8259 is ok.
>>>
>>> Signed-off-by: Wanpeng Li <liwp@linux.vnet.ibm.com>
>>> ---
>>>  hw/pc_piix.c |    3 ++-
>>>  1 files changed, 2 insertions(+), 1 deletions(-)
>>>
>>> diff --git a/hw/pc_piix.c b/hw/pc_piix.c
>>> index 63dba4e..52f7cf8 100644
>>> --- a/hw/pc_piix.c
>>> +++ b/hw/pc_piix.c
>>> @@ -210,7 +210,6 @@ static void pc_init1(MemoryRegion *system_memory,
>>>          isa_bus = isa_bus_new(NULL, system_io);
>>>          no_hpet = 1;
>>>      }
>>> -    isa_bus_irqs(isa_bus, gsi);
>>>  
>>>      if (kvm_irqchip_in_kernel()) {
>>>          i8259 = kvm_i8259_init(isa_bus);
>>> @@ -221,6 +220,8 @@ static void pc_init1(MemoryRegion *system_memory,
>>>          i8259 = i8259_init(isa_bus, cpu_irq[0]);
>>>      }
>>>  
>>> +    isa_bus_irqs(isa_bus, i8259);
>>> +
>>>      for (i = 0; i < ISA_NUM_IRQS; i++) {
>>>          gsi_state->i8259_irq[i] = i8259[i];
>>>      }
>>
>> This is bogus. isa_bus_irqs sets the output IRQs of the ISA bus. And
>> those are not only delivered to the PIC on the PIIX2, but also the
>> IOAPIC. Thus we have to pass in the GSI input lines which dispatch to
>> both. Of those lines, only the first 16 will be used by the ISA bus
>> (there is even an assert to ensure this).
>>
>> Did you see any concrete bug in the context of this logic?
>>
>> Jan
>>
> 
> Yes, but actually PIC is being used at present, whether passing qemu_irq
> 0~23 to isa_bus is not safe or not.

Sorry, IRQ routing to PIC and IOAPIC is actually not a property of the
PIIX3 but the board we emulate. And here we follow the Multiprocessor
Specification of Intel and route ISA bus IRQs to both interrupt
controllers. Thus the bus must be connected to the GSIs. And, again,
GSI[16..13] aren't referenced by the ISA bus at any time.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2012-03-12  6:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-11  7:04 [Qemu-devel] [PATCH] fix bug of isa_bus irq Wanpeng Li
2012-03-11  7:46 ` Jan Kiszka
2012-03-12  6:08   ` Wanpeng Li
2012-03-12  6:55     ` Jan Kiszka [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-03-11  6:39 Wanpeng Li

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=4F5D9DD6.4060806@web.de \
    --to=jan.kiszka@web.de \
    --cc=liwp@linux.vnet.ibm.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).