From: Logan Gunthorpe <logang@deltatee.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, Guenter Roeck <linux@roeck-us.net>,
Andrea Bolognani <abologna@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-3.2 v7 6/6] hw/riscv/virt: Connect a VirtIO net PCIe device
Date: Wed, 21 Nov 2018 15:07:32 -0700 [thread overview]
Message-ID: <17256c59-cf5e-2247-985a-84c26f9d64a9@deltatee.com> (raw)
In-Reply-To: <CAKmqyKMTxgk41cBz=hW-meCUAi-_20vguqN40f_ThRU-rsaJXA@mail.gmail.com>
On 2018-11-21 2:55 p.m., Alistair Francis wrote:
> It is required for networking for PCIe devices. What PCIe device works
> for you without this patch? Can you tell me your command line
> arguments.
I can run it without that patch using a e1000e device and it works just
fine.
Command line:
$QEMU -s -nographic -machine virt -m 2G -kernel $BBL \
-object rng-random,filename=/dev/urandom,id=rng0 \
-append "console=hvc0 ro root=/dev/vda" \
-device e1000e,netdev=net0 \
-netdev user,id=net0 \
-device virtio-rng-device,rng=rng0 \
-device virtio-blk-device,drive=hd0 \
-drive file=rootfs.img,format=raw,id=hd0 \
-device nvme,drive=nvme0,serial=nvme0 \
-drive file=nvme0.qcow2,if=none,id=nvme0
--
lspcirv-hfu-01:~#
00:00.0 Host bridge: Red Hat, Inc. QEMU PCIe Host bridge
00:01.0 Ethernet controller: Intel Corporation 82574L Gigabit Network
Connection
00:02.0 Non-Volatile memory controller: Intel Corporation QEMU NVM
Express Controller (rev 02)
root@rv-hfu-01:~#
QEMU 3.0.92 monitor - type 'help' for more information
(qemu) info pci
Bus 0, device 0, function 0:
Host bridge: PCI device 1b36:0008
PCI subsystem 1af4:1100
id ""
Bus 0, device 1, function 0:
Ethernet controller: PCI device 8086:10d3
PCI subsystem 8086:0000
IRQ 11.
BAR0: 32 bit memory at 0x40040000 [0x4005ffff].
BAR1: 32 bit memory at 0x40060000 [0x4007ffff].
BAR2: I/O at 0xffffffffffffffff [0x001e].
BAR3: 32 bit memory at 0x40080000 [0x40083fff].
BAR6: 32 bit memory at 0xffffffffffffffff [0x0003fffe].
id ""
Bus 0, device 2, function 0:
Class 0264: PCI device 8086:5845
PCI subsystem 1af4:1100
IRQ 9.
BAR0: 64 bit memory at 0x40084000 [0x40085fff].
id ""
(qemu)
next prev parent reply other threads:[~2018-11-21 22:07 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 17:02 [Qemu-devel] [PATCH for-3.2 v7 0/6] Connect a PCIe host and graphics support to RISC-V Alistair Francis
2018-11-21 17:02 ` [Qemu-devel] [PATCH for-3.2 v7 1/6] hw/riscv/virt: Increase the number of interrupts Alistair Francis
2018-11-21 17:58 ` Logan Gunthorpe
2018-11-21 18:17 ` Alistair Francis
2018-11-21 18:45 ` Logan Gunthorpe
2018-11-21 18:49 ` Alistair Francis
2018-11-21 18:56 ` Logan Gunthorpe
2018-11-21 18:59 ` Alistair Francis
2018-11-21 19:02 ` Logan Gunthorpe
2018-11-21 17:02 ` [Qemu-devel] [PATCH for-3.2 v7 2/6] hw/riscv/virt: Adjust memory layout spacing Alistair Francis
2018-11-21 17:59 ` Logan Gunthorpe
2018-11-21 17:02 ` [Qemu-devel] [PATCH for-3.2 v7 3/6] hw/riscv/virt: Connect the gpex PCIe Alistair Francis
2018-11-21 18:01 ` Logan Gunthorpe
2018-11-21 18:21 ` Alistair Francis
2018-11-21 17:02 ` [Qemu-devel] [PATCH for-3.2 v7 4/6] riscv: Enable VGA and PCIE_VGA Alistair Francis
2018-11-21 18:01 ` Logan Gunthorpe
2018-11-21 17:02 ` [Qemu-devel] [PATCH for-3.2 v7 5/6] hw/riscv/sifive_u: Connect the Xilinx PCIe Alistair Francis
2018-11-21 18:05 ` Logan Gunthorpe
2018-11-21 18:32 ` Alistair Francis
2018-11-21 18:50 ` Logan Gunthorpe
2018-11-21 19:02 ` Alistair Francis
2018-11-21 19:08 ` Logan Gunthorpe
2018-11-21 19:16 ` Alistair Francis
2018-11-21 19:19 ` Logan Gunthorpe
2018-11-21 19:21 ` Alistair Francis
2018-11-21 19:24 ` Logan Gunthorpe
2018-11-21 19:51 ` Alistair Francis
2018-11-21 21:54 ` Alistair Francis
2018-11-21 22:01 ` Logan Gunthorpe
2018-11-21 22:09 ` Alistair Francis
2018-11-21 22:11 ` Logan Gunthorpe
2018-11-21 22:15 ` Palmer Dabbelt
2018-11-21 21:37 ` Palmer Dabbelt
2018-11-21 22:01 ` Alistair Francis
2018-11-21 22:15 ` Palmer Dabbelt
2018-11-21 19:15 ` Logan Gunthorpe
2018-11-21 19:18 ` Alistair Francis
2018-11-21 19:20 ` Logan Gunthorpe
2018-11-21 21:26 ` Palmer Dabbelt
2018-11-21 21:49 ` Alistair Francis
2018-11-21 22:15 ` Palmer Dabbelt
2018-11-21 22:23 ` Alistair Francis
2018-11-21 22:36 ` Palmer Dabbelt
2018-11-21 23:10 ` Guenter Roeck
2018-11-21 23:26 ` Logan Gunthorpe
2018-11-22 2:13 ` Palmer Dabbelt
2018-11-22 2:23 ` Alistair Francis
2018-11-26 19:15 ` Palmer Dabbelt
2018-11-21 18:36 ` Guenter Roeck
2018-11-21 18:55 ` Logan Gunthorpe
2018-11-21 17:03 ` [Qemu-devel] [PATCH for-3.2 v7 6/6] hw/riscv/virt: Connect a VirtIO net PCIe device Alistair Francis
2018-11-21 18:07 ` Logan Gunthorpe
2018-11-21 18:34 ` Alistair Francis
2018-11-21 19:11 ` Logan Gunthorpe
2018-11-21 21:55 ` Alistair Francis
2018-11-21 22:07 ` Logan Gunthorpe [this message]
2018-11-21 22:11 ` Alistair Francis
2018-11-21 22:14 ` Alistair Francis
2018-11-21 22:16 ` Logan Gunthorpe
2018-11-21 22:18 ` Logan Gunthorpe
2018-11-22 10:59 ` [Qemu-devel] [PATCH for-3.2 v7 0/6] Connect a PCIe host and graphics support to RISC-V Andrea Bolognani
2018-11-26 16:03 ` Alistair Francis
2018-11-26 19:34 ` Palmer Dabbelt
2018-11-26 21:33 ` Guenter Roeck
2018-11-27 12:40 ` 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=17256c59-cf5e-2247-985a-84c26f9d64a9@deltatee.com \
--to=logang@deltatee.com \
--cc=Alistair.Francis@wdc.com \
--cc=abologna@redhat.com \
--cc=alistair23@gmail.com \
--cc=linux@roeck-us.net \
--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).