qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Andrea Bolognani <abologna@redhat.com>
To: Alistair Francis <alistair23@gmail.com>
Cc: Alistair Francis <Alistair.Francis@wdc.com>,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
	qemu-riscv@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v6 0/5] Connect a PCIe host and graphics support to RISC-V
Date: Thu, 01 Nov 2018 09:20:33 +0100	[thread overview]
Message-ID: <f91286ff09066c577d359b1d185aca9fb7d21331.camel@redhat.com> (raw)
In-Reply-To: <CAKmqyKNF+tQFf50BCj91_RypYeHbnoZLvpm8gH71iW1og9uWfA@mail.gmail.com>

On Wed, 2018-10-31 at 13:10 -0700, Alistair Francis wrote:
> On Wed, Oct 31, 2018 at 7:51 AM Andrea Bolognani <abologna@redhat.com> wrote:
> > With the pcie.0 <- pcie-root-port <- virtio-net-pci setup I get
> > 
> >   qemu-system-riscv64: -device pcie-root-port,port=0x8,chassis=1,\
> >   id=pci.1,bus=pcie.0,multifunction=on,addr=0x1: MSI-X is not \
> >   supported by interrupt controller
> > 
> > just like last time, which as I mentioned is a problem for libvirt
> > because we follow the recommendations outlined in qemu/docs/pcie.txt
> > and never plug devices into pcie.0 directly.
> 
> At the moment we can't support MSI, the interrupt controller doesn't
> support MSI.

I see. Are there plans for that to change? Will we eventually need
something like Arm's 'gic-version' machine option to pick a more
featureful interrupt controller?

Either way, as it is we certainly can't flip the default to
virtio-pci at the libvirt level quite yet, so we'll have to stick
with virtio-mmio for a while longer... Not exactly the outcome I
was hoping for :(

> > Let me know if you need me to try anything else :)
> 
> Any ideas on how to debug the confusing memory mappings or
> non-existent interrupts would be helpful :)

Sorry, not really my area of expertise O:-)

-- 
Andrea Bolognani / Red Hat / Virtualization

  reply	other threads:[~2018-11-01  8:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-30 22:17 [Qemu-devel] [PATCH v6 0/5] Connect a PCIe host and graphics support to RISC-V Alistair Francis
2018-10-30 22:17 ` [Qemu-devel] [PATCH v6 1/5] hw/riscv/virt: Increase the number of interrupts Alistair Francis
2018-10-30 22:17 ` [Qemu-devel] [PATCH v6 2/5] hw/riscv/virt: Connect the gpex PCIe Alistair Francis
2018-11-05 13:23   ` Bin Meng
2018-11-05 19:47     ` Alistair Francis
2018-11-06  6:45       ` Bin Meng
2018-11-07 21:46         ` Alistair Francis
2018-10-30 22:18 ` [Qemu-devel] [PATCH v6 3/5] riscv: Enable VGA and PCIE_VGA Alistair Francis
2018-10-30 22:18 ` [Qemu-devel] [PATCH v6 4/5] hw/riscv/sifive_u: Connect the Xilinx PCIe Alistair Francis
2018-10-30 22:18 ` [Qemu-devel] [PATCH v6 5/5] hw/riscv/virt: Connect a VirtIO net PCIe device Alistair Francis
2018-10-31 14:51 ` [Qemu-devel] [PATCH v6 0/5] Connect a PCIe host and graphics support to RISC-V Andrea Bolognani
2018-10-31 20:10   ` Alistair Francis
2018-11-01  8:20     ` Andrea Bolognani [this message]
2018-11-07 21:47       ` Alistair Francis
2018-11-13 15:52         ` Andrea Bolognani

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=f91286ff09066c577d359b1d185aca9fb7d21331.camel@redhat.com \
    --to=abologna@redhat.com \
    --cc=Alistair.Francis@wdc.com \
    --cc=alistair23@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-riscv@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).