From: Muli Ben-Yehuda <muli@il.ibm.com>
To: Avi Kivity <avi@redhat.com>
Cc: Amit Shah <amit.shah@redhat.com>,
kvm@vger.kernel.org, anthony@codemonkey.ws,
weidong.han@intel.com, allen.m.kay@intel.com,
Ben-Ami Yassour1 <BENAMI@il.ibm.com>
Subject: Re: [PATCH 3/6] qemu: piix: Introduce functions to get pin number from irq and vice versa
Date: Tue, 28 Oct 2008 17:44:58 +0200 [thread overview]
Message-ID: <20081028154458.GC6737@il.ibm.com> (raw)
In-Reply-To: <4906ED8F.3040608@redhat.com>
On Tue, Oct 28, 2008 at 12:46:39PM +0200, Avi Kivity wrote:
> Muli Ben-Yehuda wrote:
>> On Sun, Oct 26, 2008 at 03:31:24PM +0200, Avi Kivity wrote:
>>
>>> Amit Shah wrote:
>>>
>>>> +int piix3_get_pin(int pic_irq)
>>>> +{
>>>> + int i;
>>>> + for (i = 0; i < 4; i++)
>>>> + if (piix3_dev->config[0x60+i] == pic_irq)
>>>> + return i;
>>>> + return -1;
>>>> +}
>>>>
>>> What happens if two pci interrupts are routed to one irq line?
>>>
>>
>> This one I'm still thinking about.
>>
>
> Well, what is this needed for in the first place?
This specific function is not used. I assume Amit added it for
completeness with piix_get_irq. piix_get_irq, as far as I can tell, is
used in only one place (when the guest updates a device's
configuration space interrupt register) to go from interrupt pin
(intx) to guest IRQ line.
Cheers,
Muli
--
The First Workshop on I/O Virtualization (WIOV '08)
Dec 2008, San Diego, CA, http://www.usenix.org/wiov08/
<->
SYSTOR 2009---The Israeli Experimental Systems Conference
http://www.haifa.il.ibm.com/conferences/systor2009/
next prev parent reply other threads:[~2008-10-28 15:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 15:26 [v7] Userspace patches for PCI device assignment Amit Shah
2008-10-24 15:26 ` [PATCH 1/6] KVM/userspace: Device Assignment: Add ioctl wrappers needed for assigning devices Amit Shah
2008-10-24 15:26 ` [PATCH 2/6] qemu: Introduce pci_map_irq to get irq nr from pin number for a PCI device Amit Shah
2008-10-24 15:26 ` [PATCH 3/6] qemu: piix: Introduce functions to get pin number from irq and vice versa Amit Shah
2008-10-24 15:26 ` [PATCH 4/6] KVM/userspace: Build vtd.c for Intel IOMMU support Amit Shah
2008-10-24 15:26 ` [PATCH 5/6] KVM/userspace: Device Assignment: Support for assigning PCI devices to guests Amit Shah
2008-10-24 15:26 ` [PATCH 6/6] KVM/userspace: Device Assignment: Support for hot plugging PCI devices Amit Shah
2008-10-24 16:22 ` [PATCH 5/6] KVM/userspace: Device Assignment: Support for assigning PCI devices to guests Anthony Liguori
2008-10-26 12:54 ` Avi Kivity
2008-10-28 10:11 ` Muli Ben-Yehuda
2008-10-27 1:28 ` Su, Disheng
2008-10-27 6:32 ` Han, Weidong
2008-10-28 10:12 ` Muli Ben-Yehuda
2008-10-26 13:31 ` [PATCH 3/6] qemu: piix: Introduce functions to get pin number from irq and vice versa Avi Kivity
2008-10-28 10:12 ` Muli Ben-Yehuda
2008-10-28 10:46 ` Avi Kivity
2008-10-28 15:44 ` Muli Ben-Yehuda [this message]
2008-10-28 16:21 ` Avi Kivity
2008-10-28 16:45 ` Muli Ben-Yehuda
2008-10-26 13:29 ` [PATCH 1/6] KVM/userspace: Device Assignment: Add ioctl wrappers needed for assigning devices Avi Kivity
2008-10-28 10:13 ` Muli Ben-Yehuda
2008-10-24 15:59 ` [v7] Userspace patches for PCI device assignment Anthony Liguori
2008-10-28 10:13 ` Muli Ben-Yehuda
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=20081028154458.GC6737@il.ibm.com \
--to=muli@il.ibm.com \
--cc=BENAMI@il.ibm.com \
--cc=allen.m.kay@intel.com \
--cc=amit.shah@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=weidong.han@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.