From: Wei Xu <wexu2@cisco.com>
To: Isaku Yamahata <yamahata@valinux.co.jp>,
Adnan Khaleel <adnan@khaleel.us>
Cc: skandasa@cisco.com, etmartin@cisco.com, qemu-devel@nongnu.org,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: [Qemu-devel] Re: [PATCH v5 00/14] pcie port switch emulators
Date: Tue, 19 Oct 2010 16:05:28 -0700 [thread overview]
Message-ID: <C8E37248.15F4A%wexu2@cisco.com> (raw)
In-Reply-To: <20101019223915.GD30021@valinux.co.jp>
Isaku,
Good work! One question here: any plan to put q35 and seabios into mainline?
FYI: I have made pcie plus q35 working on qemu-kvm, though on a little bit
old code base.
Wei
On 10/19/10 3:39 PM, "Isaku Yamahata" <yamahata@valinux.co.jp> wrote:
> On Tue, Oct 19, 2010 at 11:07:34AM -0500, Adnan Khaleel wrote:
>> Are all these patches going to be integrated into the current qemu
>> repository?
>
> Eventually. Right now some of them are merged into Michael's pci branch.
> It's up to Michael when he requests Anthony to pull the branch.
>
> thanks,
>
>>
>> -AK
>>
>> ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
>> From: Isaku Yamahata [mailto:yamahata@valinux.co.jp]
>> To: Michael S. Tsirkin [mailto:mst@redhat.com]
>> Cc: qemu-devel@nongnu.org, skandasa@cisco.com, etmartin@cisco.com,
>> wexu2@cisco.com, adnan@khaleel.us
>> Sent: Tue, 19 Oct 2010 08:55:29 -0500
>> Subject: Re: [PATCH v5 00/14] pcie port switch emulators
>>
>>>> Isaku Yamahata (14):
>>>> pci: introduce helper functions to test-and-{clear, set} mask in
>>>> configuration space
>>>> pci: introduce helper function to handle msi-x and msi.
>>>> pci: use pci_word_test_and_clear_mask() in pci_device_reset()
>>>> pci/bridge: fix pci_bridge_reset()
>>>> msi: implements msi
>>>> pcie: add pcie constants to pcie_regs.h
>>>> pcie: helper functions for pcie capability and extended capability
>>>
>>> I'll apply these.
>>>
>>>> pcie/aer: helper functions for pcie aer capability
>>>
>>> Maybe move this to the end of the series?
>>>
>>>> pcie port: define struct PCIEPort/PCIESlot and helper functions
>>>> ioh3420: pcie root port in X58 ioh
>>>> x3130: pcie upstream port
>>>> x3130: pcie downstream port
>>>> pcie/hotplug: introduce pushing attention button command
>>>
>>> I think the above can be applied - just remove the dependency
>>> on aer for now.
>>
>> Okay. I'll update the patch series and send it tomorrow.
>>
>> --
>> yamahata
>>
next prev parent reply other threads:[~2010-10-19 23:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 16:07 [Qemu-devel] Re: [PATCH v5 00/14] pcie port switch emulators Adnan Khaleel
2010-10-19 22:39 ` Isaku Yamahata
2010-10-19 23:05 ` Wei Xu [this message]
2010-10-19 23:17 ` Isaku Yamahata
2010-10-19 23:16 ` Michael S. Tsirkin
2010-10-19 23:20 ` Wei Xu
-- strict thread matches above, loose matches on Subject: below --
2010-10-19 9:06 [Qemu-devel] " Isaku Yamahata
2010-10-19 11:51 ` [Qemu-devel] " Michael S. Tsirkin
2010-10-19 15:19 ` Isaku Yamahata
2010-10-19 17:06 ` Michael S. Tsirkin
2010-10-19 22:36 ` Isaku Yamahata
2010-10-19 22:40 ` Michael S. Tsirkin
2010-10-19 22:55 ` Isaku Yamahata
2010-10-19 23:02 ` Michael S. Tsirkin
2010-10-19 11:56 ` Michael S. Tsirkin
2010-10-19 13:55 ` Isaku Yamahata
2010-10-19 13:00 ` Michael S. Tsirkin
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=C8E37248.15F4A%wexu2@cisco.com \
--to=wexu2@cisco.com \
--cc=adnan@khaleel.us \
--cc=etmartin@cisco.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=skandasa@cisco.com \
--cc=yamahata@valinux.co.jp \
/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).