From: Claudio Fontana <claudio.fontana@huawei.com>
To: Alvise Rigo <a.rigo@virtualopensystems.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: Rob Herring <rob.herring@linaro.org>,
"tech@virtualopensystems.com" <tech@virtualopensystems.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RFC PATCH 0/8] Add Generic PCI host device update
Date: Tue, 9 Sep 2014 18:35:14 +0200 [thread overview]
Message-ID: <540F2C42.9060307@huawei.com> (raw)
In-Reply-To: <53BFAE4A.7070609@virtualopensystems.com>
On 11.07.2014 11:28, Alvise Rigo wrote:
> The kernel version is a very recent one: v3.16.0-rc1.
> Maybe you are right. I will test some older version to see if I'm able
> to reproduce the issue.
>
> Thank you,
> alvise
Any news on this?
I will be soon in the situation when I can start testing these as the way to get PCI working in OSv for AArch64,
but will require a bit more time, since there is some more mechanical work involved.
Ciao,
Claudio
> Il 11/07/2014 11:09, Peter Maydell ha scritto:
>> On 11 July 2014 08:21, Alvise Rigo <a.rigo@virtualopensystems.com> wrote:
>>> This work has been tested attaching several PCI devices to the mach-virt
>>> platform. The tested devices are: virtio-blk-pci, virtio-net-pci,
>>> lsi53c895a and pci-ohci (all attached at the same time).
>>> Even if the original work was not changed in its core functionalities, I
>>> couldn't reproduce the malfunctioning of the LSI SCSI mentioned in [1].
>>> After attaching several qcow2 images, formatting and filling them, I
>>> didn't notice anything wrong. Am I missing something?
>>
>> Interesting. Perhaps the bug was on the kernel side; which
>> guest kernel version are you using to test with?
>>
>> thanks
>> -- PMM
>>
>
next prev parent reply other threads:[~2014-09-09 16:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 7:21 [Qemu-devel] [RFC PATCH 0/8] Add Generic PCI host device update Alvise Rigo
2014-07-11 7:21 ` [Qemu-devel] [RFC PATCH 1/8] mach-virt: move GIC inside mach-virt structure Alvise Rigo
2014-07-11 7:21 ` [Qemu-devel] [RFC PATCH 2/8] mach-virt: improve PCI memory topology definition Alvise Rigo
2014-07-11 7:21 ` [Qemu-devel] [RFC PATCH 3/8] QEMUMachine: finalize_dt function Alvise Rigo
2014-07-11 7:21 ` [Qemu-devel] [RFC PATCH 4/8] generic_pci: create header file Alvise Rigo
2014-07-11 7:21 ` [Qemu-devel] [RFC PATCH 5/8] generic_pci: create own map irq function Alvise Rigo
2014-07-11 7:21 ` [Qemu-devel] [RFC PATCH 6/8] generic_pci: generate dt node after devices init Alvise Rigo
2014-11-05 12:26 ` Claudio Fontana
2014-11-06 10:27 ` alvise rigo
2014-07-11 7:21 ` [Qemu-devel] [RFC PATCH 7/8] generic_pci: realize device with machine data Alvise Rigo
2014-07-11 7:21 ` [Qemu-devel] [RFC PATCH 8/8] generic_pci: add interrupt map structures Alvise Rigo
2014-07-11 9:09 ` [Qemu-devel] [RFC PATCH 0/8] Add Generic PCI host device update Peter Maydell
2014-07-11 9:28 ` Alvise Rigo
2014-07-13 14:28 ` Rob Herring
2014-09-09 16:35 ` Claudio Fontana [this message]
2014-09-10 7:31 ` alvise rigo
2014-11-05 10:23 ` Claudio Fontana
2014-11-05 11:09 ` alvise rigo
2014-11-07 15:40 ` Claudio Fontana
2014-11-10 10:00 ` alvise rigo
2014-11-11 3:24 ` Ming Lei
2014-11-11 4:22 ` Ming Lei
2014-11-11 10:26 ` Claudio Fontana
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=540F2C42.9060307@huawei.com \
--to=claudio.fontana@huawei.com \
--cc=a.rigo@virtualopensystems.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rob.herring@linaro.org \
--cc=tech@virtualopensystems.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.