On Thu, 24 May 2018 14:24:32 +0200
Xiao Feng Ren wrote:
> From: Yi Min Zhao
>
> This commit adds hotplug support for PCI devices on S390 guests.
> There's no need to implement hot unplug for zPCI as QEMU implements
> an unplug callback which will unplug both PCI and zPCI device in a
> cascaded
On Mon, 28 May 2018 16:26:57 +0800
Xiao Feng Ren wrote:
> On 5/25/2018 6:22 PM, Bjoern Walk wrote:
> > Cornelia Huck [2018-05-24, 06:25PM +0200]:
> >> On Thu, 24 May 2018 14:24:32 +0200
> >> Xiao Feng Ren wrote:
> >>
> >>> From: Yi Min Zhao
On Fri, 1 Jun 2018 12:43:09 +0800
Yi Min Zhao wrote:
> 在 2018/5/29 下午5:04, Cornelia Huck 写道:
> > On Mon, 28 May 2018 16:26:57 +0800
> > Xiao Feng Ren wrote:
> >> As the model of Shmem is not support in qemu, the rng device doesn't
> >> support MSI-X. So
On Mon, 4 Jun 2018 16:17:52 +0200
Ján Tomko wrote:
> On Mon, Jun 04, 2018 at 02:05:17PM +0800, Yi Min Zhao wrote:
> >
> >
> >在 2018/6/2 下午10:18, Ján Tomko 写道:
> >> On Thu, May 24, 2018 at 02:24:30PM +0200, Xiao Feng Ren wrote:
> >>> From: Yi Min Zhao
> >>>
> >>> The pci-root depends on zpci
On Tue, 3 Jul 2018 13:32:29 +0200
Kevin Wolf wrote:
> > > > Has serial/gemoetry been fixed meanwhile and will it make it into the
> > > > next release?
> > >
> > > I cannot find an archive that has it, but it is on the libvirt mailing
> > > list as "[libvirt] [PATCH v3] qemu: format serial and
On Wed, 4 Jul 2018 15:34:40 +0200
Kevin Wolf wrote:
> Am 04.07.2018 um 15:02 hat Cornelia Huck geschrieben:
> > On Tue, 3 Jul 2018 13:32:29 +0200
> > Kevin Wolf wrote:
> >
> > > > > > Has serial/gemoetry been fixed meanwhile and will it make it into
&
On Wed, 4 Jul 2018 17:14:02 +0100
Peter Maydell wrote:
> On 4 July 2018 at 14:34, Kevin Wolf wrote:
> > Essentially, what is important to me isn't getting these options dropped
> > exactly in 3.0, but not setting a bad precedence that deprecation isn't
> > actually worth anything. We may easily
On Mon, 09 Jul 2018 08:33:05 +0200
Markus Armbruster wrote:
> Peter Maydell writes:
>
> > On 6 July 2018 at 15:56, Kevin Wolf wrote:
> >> Am 06.07.2018 um 13:11 hat Cornelia Huck geschrieben:
> >>> That way, we can still easily remove old cruft (case
On Mon, 9 Jul 2018 08:58:05 +0200
Thomas Huth wrote:
> On 06.07.2018 13:11, Cornelia Huck wrote:
> > On Wed, 4 Jul 2018 17:14:02 +0100
> > Peter Maydell wrote:
> >
> >> On 4 July 2018 at 14:34, Kevin Wolf wrote:
> >>> Essentially, what is i
On Tue, 10 Jul 2018 07:59:15 +0200
Markus Armbruster wrote:
> In addition to actively pulling libvirt developers into review of
> deprecation patches, we should pursue the idea to optionally let QEMU
> fail on use of deprecated features, then have libvirt run its test suite
> that way.
What abou
On Tue, 10 Jul 2018 16:39:31 +0200
Peter Krempa wrote:
> On Tue, Jul 10, 2018 at 16:22:08 +0200, Cornelia Huck wrote:
> > On Tue, 10 Jul 2018 07:59:15 +0200
> > Markus Armbruster wrote:
> >
> > > In addition to actively pulling libvirt developers into review of
On Wed, 11 Jul 2018 08:53:20 +0200
Thomas Huth wrote:
> On 10.07.2018 17:24, Peter Krempa wrote:
> > On Tue, Jul 10, 2018 at 17:01:22 +0200, Cornelia Huck wrote:
> >> So, from that I gather that a hard failure would be the easiest for
> >> libvirt to detect (and e
On Thu, 12 Jul 2018 08:51:16 +0200
Markus Armbruster wrote:
> Markus Armbruster writes:
>
> > Kevin Wolf writes:
> >
> >> Am 10.07.2018 um 16:22 hat Cornelia Huck geschrieben:
> >>> On Tue, 10 Jul 2018 07:59:15 +0200
> >>> Markus Armbrust
On Thu, 12 Jul 2018 17:47:00 +0200
Thomas Huth wrote:
> On 12.07.2018 08:32, Markus Armbruster wrote:
> > Daniel P. Berrangé writes:
> [...]
> >> For libvirt, I think whenever something is proposed for deprecation
> >> we could just CC libvir-list, or ask one of the libvirt people to
> >> conf
iles changed, 235 insertions(+), 234 deletions(-)
> create mode 100644 qemu-deprecated.texi
Reviewed-by: Cornelia Huck
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
nged, 4 insertions(+)
Reviewed-by: Cornelia Huck
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
On Mon, 16 Jul 2018 09:54:12 +0200
Thomas Huth wrote:
> On 16.07.2018 09:32, Markus Armbruster wrote:
> > Libvirt developers would like to be copied on patches to qemu-doc
> > appendix "Deprecated features". Do them the favor.
> >
> > Signed-off-by: Markus Armbruster
> > ---
> > MAINTAINERS |
On Tue, 10 Jul 2018 16:02:14 +0800
Yi Min Zhao wrote:
> Abstract
>
> The PCI representation in QEMU has recently been extended for S390
> allowing configuration of zPCI attributes like uid (user-defined
> identifier) and fid (PCI function identifier).
> The details can be found here:
> h
On Tue, 24 Jul 2018 10:20:48 +0200
Andrea Bolognani wrote:
> Looking at both the generated QEMU command line and the qemu-devel
> message linked above, I seem to understand the zpci device is
> basically some sort of adapter that sits between a regular PCI
> device (emulated or otherwise) and an
This option has been deprecated for two releases; remove it.
Signed-off-by: Cornelia Huck
---
hw/s390x/3270-ccw.c| 2 +-
hw/s390x/css-bridge.c | 1 -
hw/s390x/css.c | 6 ++
hw/s390x/s390-ccw.c| 2 +-
hw/s390x/s390-virtio
On Tue, 24 Jul 2018 13:15:50 +0200
Peter Krempa wrote:
> On Tue, Jul 24, 2018 at 11:24:13 +0200, Cornelia Huck wrote:
> > This option has been deprecated for two releases; remove it.
> >
> > Signed-off-by: Cornelia Huck
> > ---
> > hw/s390x/3270-ccw.c
On Tue, 24 Jul 2018 18:08:21 +0200
Jiri Denemark wrote:
> On Mon, Jul 23, 2018 at 17:45:33 -0400, Collin Walling wrote:
> > Use model name "qemu" instead of "max" when calling
> > query-cpu-model-expansion for s390 on tcg.
> >
> > Signed-off-by: Collin Walling
> > ---
> > src/qemu/qemu_capabil
On Wed, 25 Jul 2018 09:34:08 +0200
David Hildenbrand wrote:
> On 25.07.2018 01:02, Collin Walling wrote:
> > Thanks for expanding on what the "max" model name is suppose to be. I
> > wonder if a
> > s/"qemu"/"max" in QEMU would suffice (I'm taking a shot in the dark here.)
>
> Nope, it dynam
On Thu, 26 Jul 2018 15:50:28 +0200
Erik Skultety wrote:
> On Tue, Jul 24, 2018 at 11:44:40AM -0600, Alex Williamson wrote:
> > On Fri, 20 Jul 2018 10:19:24 +0800
> > Zhenyu Wang wrote:
> >
> > > Current mdev device create interface depends on fixed mdev type, which
> > > get uuid
> > > from u
On Fri, 20 Jul 2018 10:19:25 +0800
Zhenyu Wang wrote:
> For special mdev type which can aggregate instances for mdev device,
> this extends mdev create interface by allowing extra "instances=xxx"
> parameter, which is passed to mdev device model to be able to create
> arbitrary bundled number of
On Fri, 20 Jul 2018 10:19:28 +0800
Zhenyu Wang wrote:
> Update mdev doc on new aggregration attribute and instances attribute
> for mdev.
>
> Cc: Kirti Wankhede
> Cc: Alex Williamson
> Cc: Kevin Tian
> Signed-off-by: Zhenyu Wang
> ---
> Documentation/vfio-mediated-device.txt | 39 ++
On Thu, 26 Jul 2018 09:51:26 -0600
Alex Williamson wrote:
> On Thu, 26 Jul 2018 17:30:07 +0200
> Cornelia Huck wrote:
>
> > On Thu, 26 Jul 2018 15:50:28 +0200
> > Erik Skultety wrote:
> > > Since libvirt doesn't have an API to create mdevs yet, this doesn&
On Thu, 26 Jul 2018 17:43:45 +0200
Erik Skultety wrote:
> On Thu, Jul 26, 2018 at 05:30:07PM +0200, Cornelia Huck wrote:
> > One thing I noticed is that we have seem to have an optional (?)
> > vendor-driver created "aggregation" attribute (which always prints
>
On Fri, 27 Jul 2018 10:16:58 +0800
Zhenyu Wang wrote:
> On 2018.07.26 17:46:40 +0200, Cornelia Huck wrote:
> > On Fri, 20 Jul 2018 10:19:28 +0800
> > Zhenyu Wang wrote:
> >
> > > Update mdev doc on new aggregration attribute and instances attribute
> >
On Tue, 24 Jul 2018 11:24:13 +0200
Cornelia Huck wrote:
> This option has been deprecated for two releases; remove it.
>
> Signed-off-by: Cornelia Huck
> ---
> hw/s390x/3270-ccw.c| 2 +-
> hw/s390x/css-bridge.c | 1 -
> hw/s390x/css.c
On Thu, 2 Aug 2018 09:34:37 +0800
Fam Zheng wrote:
> On Wed, Aug 1, 2018 at 9:18 PM Cornelia Huck wrote:
> >
> > On Wed, 1 Aug 2018 15:11:23 +0200
> > Cornelia Huck wrote:
> >
> > > On Wed, 1 Aug 2018 14:54:51 +0200
> > > Cornelia Huck wrote
On Thu, 2 Aug 2018 09:15:24 +0200
Cornelia Huck wrote:
> On Thu, 2 Aug 2018 09:34:37 +0800
> Fam Zheng wrote:
>
> > On Wed, Aug 1, 2018 at 9:18 PM Cornelia Huck wrote:
> > >
> > > On Wed, 1 Aug 2018 15:11:23 +0200
> > > Cornelia Huck wrote:
>
On Thu, 2 Aug 2018 09:33:48 +0200
Cornelia Huck wrote:
> On Thu, 2 Aug 2018 09:15:24 +0200
> Cornelia Huck wrote:
>
> > On Thu, 2 Aug 2018 09:34:37 +0800
> > Fam Zheng wrote:
> >
> > > On Wed, Aug 1, 2018 at 9:18 PM Cornelia Huck wrote:
> > &g
On Wed, 1 Aug 2018 18:21:27 +0800
Fam Zheng wrote:
> On Tue, 07/24 11:24, Cornelia Huck wrote:
> > diff --git a/hw/s390x/css-bridge.c b/hw/s390x/css-bridge.c
> > index a02d708239..1bd6c8b458 100644
> > --- a/hw/s390x/css-bridge.c
> > +++ b/hw/s390x/css-br
On Wed, 1 Aug 2018 14:54:51 +0200
Cornelia Huck wrote:
> On Wed, 1 Aug 2018 18:21:27 +0800
> Fam Zheng wrote:
>
> > On Tue, 07/24 11:24, Cornelia Huck wrote:
> > > diff --git a/hw/s390x/css-bridge.c b/hw/s390x/css-bridge.c
> > > index a02d708239..1bd6c8b45
On Wed, 1 Aug 2018 15:11:23 +0200
Cornelia Huck wrote:
> On Wed, 1 Aug 2018 14:54:51 +0200
> Cornelia Huck wrote:
>
> > On Wed, 1 Aug 2018 18:21:27 +0800
> > Fam Zheng wrote:
> >
> > > On Tue, 07/24 11:24, Cornelia Huck wrote:
> > > > d
On Mon, 13 Aug 2018 12:46:16 +0800
Yi Min Zhao wrote:
> Is there any comment? I expect comments from all of you.
Well, I don't have any objections from my side, but you need the
libvirt folks' opinion on this.
>
>
> 在 2018/8/7 下午5:10, Yi Min Zhao 写道:
> > Abstract
> >
> > The PCI repr
On Thu, 16 Aug 2018 16:52:18 +0200
Andrea Bolognani wrote:
> On Tue, 2018-08-07 at 17:10 +0800, Yi Min Zhao wrote:
> > The pci-root depends on zpci capability. So autogenerate pci-root if
> > zpci exists.
> >
> > Signed-off-by: Yi Min Zhao
> > Reviewed-by: Boris Fiuczynski
> > Reviewed-by: Ste
by: Thomas Huth
> ---
> docs/virtio-balloon-stats.txt | 6 +++---
> qemu-deprecated.texi | 5 -
> qemu-options.hx | 10 --
> vl.c | 36
> 4 files changed, 3 insertions(+), 54 deletions(-)
On Thu, 15 Nov 2018 10:05:59 +
Daniel P. Berrangé wrote:
> On Wed, Nov 14, 2018 at 09:38:31PM -0200, Eduardo Habkost wrote:
> > Many of the current virtio-*-pci device types actually represent
> > 3 different types of devices:
> > * virtio 1.0 non-transitional devices
> > * virtio 1.0 transit
On Wed, 14 Nov 2018 21:38:31 -0200
Eduardo Habkost wrote:
> diff --git a/hw/virtio/virtio-pci.h b/hw/virtio/virtio-pci.h
> index 813082b0d7..1d2a11504f 100644
> --- a/hw/virtio/virtio-pci.h
> +++ b/hw/virtio/virtio-pci.h
(...)
> +/**
> + * VirtioPCIDeviceTypeInfo:
> + *
> + * Template for virti
On Thu, 15 Nov 2018 12:21:55 +0100
Cornelia Huck wrote:
> After a quick look, this seems fine; have not actually tried to run it
> yet.
Played a bit with it (with zpci devices for a s390x machine), seems to
work as expected.
--
libvir-list mailing list
libvir-list@redhat.com
On Fri, 16 Nov 2018 01:45:51 -0200
Eduardo Habkost wrote:
> On Thu, Nov 15, 2018 at 05:29:24PM +0100, Andrea Bolognani wrote:
> > One thing that I'm very much not convinced about is the naming,
> > specifically leaving the virtio revision out: I get it that we
> > Should Never Need™ another majo
On Mon, 19 Nov 2018 13:07:59 -0500
"Michael S. Tsirkin" wrote:
> On Mon, Nov 19, 2018 at 11:41:05AM +0100, Cornelia Huck wrote:
> > On Fri, 16 Nov 2018 01:45:51 -0200
> > Eduardo Habkost wrote:
> >
> > > On Thu, Nov 15, 2018 at 05:29:24PM +0100, And
On Mon, 19 Nov 2018 13:42:58 -0500
"Michael S. Tsirkin" wrote:
> On Mon, Nov 19, 2018 at 07:32:38PM +0100, Cornelia Huck wrote:
> > On Mon, 19 Nov 2018 13:07:59 -0500
> > "Michael S. Tsirkin" wrote:
> > > And I strongly believe command line users r
On Mon, 19 Nov 2018 19:32:32 -0200
Eduardo Habkost wrote:
> However, I wish this kind of usability magic didn't automatically
> imposed us the burden of keeping guest ABI compatibility too.
> Keeping ABI compatibility on the machine-friendly device types and
> interfaces is already hard enough.
On Mon, 19 Nov 2018 22:44:54 -0200
Eduardo Habkost wrote:
> On Thu, Nov 15, 2018 at 11:50:56AM +0100, Cornelia Huck wrote:
> > On Thu, 15 Nov 2018 10:05:59 +
> > Daniel P. Berrangé wrote:
> > > If libvirt did this compatibility approach, can you
> > > con
+const char *parent;
> +
> +/* Same as TypeInfo fields: */
> +size_t instance_size;
> +void (*instance_init)(Object *obj);
> +void (*class_init)(ObjectClass *klass, void *data);
> +} VirtioPCIDeviceTypeInfo;
That's a bit of boilerplate, but the end result seems t
-> v2:
> * Removed *-0.9 devices. Nobody will want to use them, if
> transitional devices work with legacy drivers
> (Gerd Hoffmann, Michael S. Tsirkin)
> * Drop virtio version from name: rename -1.0-transitional to
> -transitional (Michael S. Tsirkin)
> * Renamed -1.0 t
On Thu, 6 Jun 2019 10:15:52 -0600
Alex Williamson wrote:
> On Thu, 6 Jun 2019 09:32:24 -0600
> Alex Williamson wrote:
>
> > On Thu, 6 Jun 2019 16:44:17 +0200
> > Cornelia Huck wrote:
> >
> > > Add a rough implementation for vfio-ap.
>
On Wed, 19 Jun 2019 08:28:02 +0100
Daniel P. Berrangé wrote:
> On Tue, Jun 18, 2019 at 04:12:10PM -0600, Alex Williamson wrote:
> > On Tue, 18 Jun 2019 14:48:11 +0200
> > Sylvain Bauza wrote:
> >
> > > On Tue, Jun 18, 2019 at 1:01 PM Cornelia Huck wrote:
&g
On Wed, 19 Jun 2019 11:04:15 +0200
Sylvain Bauza wrote:
> On Wed, Jun 19, 2019 at 12:27 AM Alex Williamson
> wrote:
>
> > On Tue, 18 Jun 2019 14:48:11 +0200
> > Sylvain Bauza wrote:
> >
> > > On Tue, Jun 18, 2019 at 1:01 PM Cornelia Huck wrote:
> &
On Tue, 25 Jun 2019 16:52:51 -0600
Alex Williamson wrote:
> Hi,
>
> Based on the discussions we've had, I've rewritten the bulk of
> mdevctl. I think it largely does everything we want now, modulo
> devices that will need some sort of 1:N values per key for
> configuration in the config file ve
On Wed, 26 Jun 2019 19:53:50 -0600
Alex Williamson wrote:
> On Wed, 26 Jun 2019 08:37:20 -0600
> Alex Williamson wrote:
>
> > On Wed, 26 Jun 2019 11:58:06 +0200
> > Cornelia Huck wrote:
> >
> > > On Tue, 25 Jun 2019 16:52:51 -0600
> > >
On Thu, 27 Jun 2019 19:57:04 -0600
Alex Williamson wrote:
> On Thu, 27 Jun 2019 15:15:02 -0600
> Alex Williamson wrote:
>
> > On Thu, 27 Jun 2019 09:38:32 -0600
> > Alex Williamson wrote:
> > > > On 6/27/19 8:26 AM, Cornelia Huck wrote:
> > &
On Fri, 28 Jun 2019 11:05:46 -0600
Alex Williamson wrote:
> On Fri, 28 Jun 2019 11:06:48 +0200
> Cornelia Huck wrote:
> > What do you think of a way to specify JSON for the attributes directly
> > on the command line? Or would it be better to just edit the config
On Mon, 1 Jul 2019 08:40:51 -0600
Alex Williamson wrote:
> On Mon, 1 Jul 2019 10:20:43 +0200
> Cornelia Huck wrote:
>
> > On Fri, 28 Jun 2019 11:05:46 -0600
> > Alex Williamson wrote:
> >
> > > On Fri, 28 Jun 2019 11:06:48 +0200
> > > Corneli
On Tue, 17 Sep 2019 14:02:59 +0100
Stefan Hajnoczi wrote:
> Hi,
> LWN.net is a popular open source news site that covers Linux and other
> open source communities (Python, GNOME, Debian, etc). It has published
> a few KVM articles in the past too.
>
> Let's raise awareness of QEMU, KVM, and lib
On Wed, 11 Apr 2018 17:49:51 +0200
Shalini Chellathurai Saroja wrote:
> Let us support the basic channel I/O passthrough infrastructure based on
> vfio, which have been introduced in QEMU 2.10. The current focus is to
> support dasd-eckd (cu_type/dev_type = 0x3990/0x3390) as the target
> device.
On Wed, 11 Apr 2018 17:49:53 +0200
Shalini Chellathurai Saroja wrote:
> Let us introduce the capability vfio-ccw for supporting the basic
> channel I/O passthrough, which have been introduced in QEMU 2.10. The
> current focus is to support dasd-eckd (cu_type/dev_type = 0x3990/0x3390)
> as the tar
On Thu, 11 Aug 2016 16:17:10 +0200
Ján Tomko wrote:
> On Thu, Aug 11, 2016 at 02:31:55PM +0100, Daniel P. Berrange wrote:
> >On Thu, Aug 11, 2016 at 03:25:53PM +0200, Ján Tomko wrote:
> >> On Thu, Aug 11, 2016 at 01:00:08PM +0100, Daniel P. Berrange wrote:
> >> > On Wed, Aug 10, 2016 at 03:27:15P
[I've browsed through the thread a bit, but as I'm not a libvirt
developer I may be missing some basic things]
On Wed, 7 Sep 2016 16:34:17 -0400
Laine Stump wrote:
> On 09/07/2016 03:38 PM, Sascha Silbe wrote:
> > Dear Laine,
> >
> > Laine Stump writes:
> >
> >> On 09/07/2016 02:35 PM, Sascha S
On Mon, 19 Sep 2016 22:07:13 +0300
"Michael S. Tsirkin" wrote:
> On Wed, Sep 07, 2016 at 09:38:04PM +0200, Sascha Silbe wrote:
> > Dear Laine,
> >
> > Laine Stump writes:
> >
> > > On 09/07/2016 02:35 PM, Sascha Silbe wrote:
> > >> "Daniel P. Berrange" writes:
> > >> [...]
> > >>>
l"
> runnable all the time, while relying on the CPU model to reject invalid
> migration attempts.
>
> Suggested-by: David Hildenbrand
> Signed-off-by: Christian Borntraeger
> ---
> hw/s390x/s390-virtio-ccw.c | 8
> include/hw/s390x/s390-virtio-ccw.h |
On Fri, 27 Oct 2017 14:42:57 +0200
Christian Borntraeger wrote:
> Yes, we should also replace that with
>
> return s390_has_feat(S390_FEAT_GUARDED_STORAGE)
>
> I can fixup my patch or provide a 2nd one.
>
Consider a fixed up patch acked by me.
--
libvir-list mailing list
libvir-list@redhat.
On Thu, 24 Nov 2016 12:51:19 +1100
David Gibson wrote:
> On Wed, Nov 23, 2016 at 03:10:47PM -0200, Eduardo Habkost wrote:
> > (CCing the maintainers of the machines that crash when using
> > -nodefaults)
> >
> > On Tue, Nov 22, 2016 at 08:34:50PM -0200, Eduardo Habkost wrote:
> > [...]
> > > "de
-
> 2 files changed, 42 insertions(+), 42 deletions(-)
Unrelated to your patch, line 143 in removed-features.rst reads
``-vnc ...,tls=...``, ``-vnc ...,x509=...`` & ``-vnc ...,x509verify=...``
and is missing the release it was removed in (presumably 3.1?)
Anyway,
Reviewed-by: Cornelia Huck
Signed-off-by: Cornelia Huck
---
virt-tools/config.ini | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/virt-tools/config.ini b/virt-tools/config.ini
index f56495a26fd8..89b4e5ae6f91 100644
--- a/virt-tools/config.ini
+++ b/virt-tools/config.ini
@@ -162,7 +162,7 @@ name
On Tue, Nov 02 2021, Daniel P. Berrangé wrote:
> On Tue, Nov 02, 2021 at 12:10:42PM +0100, Cornelia Huck wrote:
>> Signed-off-by: Cornelia Huck
>> ---
>> virt-tools/config.ini | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --g
On Tue, 14 Apr 2020 19:53:05 +0200
Andrea Bolognani wrote:
> This document describes the relationship between PCI addresses as
> seen in the domain XML and by the guest OS, which is a topic that
> people get confused by time and time again.
>
> Signed-off-by: Andrea Bolognani
> ---
> docs/form
Add some information on how pci address work on s390x.
Signed-off-by: Cornelia Huck
---
docs/pci-addresses.rst | 63 ++
1 file changed, 63 insertions(+)
diff --git a/docs/pci-addresses.rst b/docs/pci-addresses.rst
index 923783a151b0..9e241a24fcfb 100644
On Tue, 14 Apr 2020 23:06:47 +0200
Boris Fiuczynski wrote:
> On 4/15/20 12:51 PM, Cornelia Huck wrote:
> > +zPCI addresses
> > +==
> > +
> > +For s390x machines, PCI addresses are handled yet differently. No
> > +topology information is relayed i
On Wed, 15 Apr 2020 16:23:46 +0200
Boris Fiuczynski wrote:
> On 4/15/20 3:42 PM, Cornelia Huck wrote:
> > On Tue, 14 Apr 2020 23:06:47 +0200
> > Boris Fiuczynski wrote:
> >
> >> On 4/15/20 12:51 PM, Cornelia Huck wrote:
> >>> +In th
On Wed, 15 Apr 2020 18:38:06 +0200
Andrea Bolognani wrote:
> On Wed, 2020-04-15 at 16:45 +0200, Cornelia Huck wrote:
> > On Wed, 15 Apr 2020 16:23:46 +0200
> > Boris Fiuczynski wrote:
> > > Once I understand you confusion above I will provide a patch...
> &
drea Bolognani
> ---
> docs/pci-addresses.rst | 60 ++
> 1 file changed, 32 insertions(+), 28 deletions(-)
Reviewed-by: Cornelia Huck
lognani
> ---
> docs/pci-addresses.rst | 57 +-
> 1 file changed, 28 insertions(+), 29 deletions(-)
Not including a 'wonky cases' category is fine with me :)
Reviewed-by: Cornelia Huck
On Wed, 15 Apr 2020 19:31:35 +0200
Andrea Bolognani wrote:
> Signed-off-by: Andrea Bolognani
> ---
> docs/pci-addresses.rst | 2 --
> 1 file changed, 2 deletions(-)
Yeah, not that useful.
Reviewed-by: Cornelia Huck
On Wed, 15 Apr 2020 19:31:36 +0200
Andrea Bolognani wrote:
> The idea behind this document is to show, with actual examples,
> that users should not expect PCI addresses in the domain XML and
> in the guest OS to match.
>
> The first zPCI example already serves this purpose perfectly, so
> in th
On Thu, 16 Apr 2020 09:28:58 +0200
Andrea Bolognani wrote:
> On Wed, 2020-04-15 at 19:47 +0200, Cornelia Huck wrote:
> > On Wed, 15 Apr 2020 19:31:36 +0200
> > Andrea Bolognani wrote:
> > > -Therefore, replacing the virtio-net device definition with the following
ect that each PCI device would show up in the guest OS with
> +a PCI address that matches the one present in the corresponding
> + element of the domain XML, but that's not guaranteed
> +to happen and will in fact not be the case in all but the simplest
> +scenarios.
>
>
&
On Thu, 16 Apr 2020 17:56:18 +0200
Boris Fiuczynski wrote:
> Improving the zPCI example by choosing more distinct values and
> adding explanation for fid.
>
> Signed-off-by: Boris Fiuczynski
> ---
> docs/pci-addresses.rst | 15 ---
> 1 file changed, 8 insertions(+), 7 deletions(-)
On Mon, 13 Apr 2020 01:52:01 -0400
Yan Zhao wrote:
> This patchset introduces a migration_version attribute under sysfs of VFIO
> Mediated devices.
>
> This migration_version attribute is used to check migration compatibility
> between two mdev devices.
>
> Currently, it has two locations:
> (1
On Fri, 17 Apr 2020 10:50:02 +0200
Boris Fiuczynski wrote:
> On 4/16/20 6:14 PM, Cornelia Huck wrote:
> > On Thu, 16 Apr 2020 17:56:18 +0200
> > Boris Fiuczynski wrote:
> >
> >> Improving the zPCI example by choosing more distinct values and
> >> addin
On Fri, 17 Apr 2020 05:52:02 -0400
Yan Zhao wrote:
> On Fri, Apr 17, 2020 at 04:44:50PM +0800, Cornelia Huck wrote:
> > On Mon, 13 Apr 2020 01:52:01 -0400
> > Yan Zhao wrote:
> >
> > > This patchset introduces a migration_version attribute under sysfs
On Fri, 17 Apr 2020 13:29:43 +0200
Boris Fiuczynski wrote:
> On 4/17/20 11:02 AM, Cornelia Huck wrote:
> > On Fri, 17 Apr 2020 10:50:02 +0200
> > Boris Fiuczynski wrote:
> >
> >> On 4/16/20 6:14 PM, Cornelia Huck wrote:
> >>> On Thu, 16 Apr 2020 17
12 insertions(+), 10 deletions(-)
Reviewed-by: Cornelia Huck
diated devices with
> +``virNodeDeviceCreateXML()``.
> +
>* qemu: Implement memory failure event
>
> New event is implemented that is emitted whenever a guest encounters a
Reviewed-by: Cornelia Huck
On Fri, 20 Nov 2020 03:51:07 +0100
Halil Pasic wrote:
> On Tue, 17 Nov 2020 04:26:05 +0100
> Eric Farman wrote:
>
> > Now that the vfio-ccw code has a notifier interface to request that
> > a device be unplugged, let's wire that together.
>
> I'm aware of the fact that performing an unplug i
On Wed, 25 Nov 2020 12:06:46 +0100
Thomas Huth wrote:
> Newer versions of the QEMU guest agent will provide the CCW address
> of devices on s390x. Store this information in the qemuAgentDiskInfo
> so that we can use this later.
>
> We also map the CSSID 0 from the guest to the value 0xfe on the
files changed, 16 insertions(+), 4 deletions(-)
Keeping my limited libvirt knowledge in mind:
Reviewed-by: Cornelia Huck
On Wed, 25 Nov 2020 12:06:48 +0100
Thomas Huth wrote:
> On s390x, devices are attached to the channel IO subsytem by default,
s/attached to the channel IO subsystem/accessed via the channel subsystem/
> so we need to look up scsi controllers via their CCW address there
> instead of using PCI.
>
On Mon, 30 Nov 2020 11:18:20 +0100
Michal Privoznik wrote:
> On 11/30/20 10:38 AM, Thomas Huth wrote:
> > On 27/11/2020 16.02, Michal Privoznik wrote:
> >> Signed-off-by: Michal Privoznik
> >> ---
> >> src/qemu/qemu_domain_address.c | 10 --
> >> 1 file changed, 4 insertions(+), 6 d
On Fri, 4 Dec 2020 16:31:56 +0100
Boris Fiuczynski wrote:
> On 12/4/20 11:24 AM, Erik Skultety wrote:
> > On Thu, Dec 03, 2020 at 06:59:32PM +0100, Shalini Chellathurai Saroja
> > wrote:
> >> Add support for AP card devices, AP queues and AP matrix devices in
> >> libvirt node device driver.
>
[sorry about not chiming in earlier]
On Wed, 29 Jul 2020 16:05:03 +0800
Yan Zhao wrote:
> On Mon, Jul 27, 2020 at 04:23:21PM -0600, Alex Williamson wrote:
(...)
> > Based on the feedback we've received, the previously proposed interface
> > is not viable. I think there's agreement that the us
On Wed, 05 Aug 2020 12:35:01 +0100
Sean Mooney wrote:
> On Wed, 2020-08-05 at 12:53 +0200, Jiri Pirko wrote:
> > Wed, Aug 05, 2020 at 11:33:38AM CEST, yan.y.z...@intel.com wrote:
(...)
> > >software_version: device driver's version.
> > > in .[.bugfix] scheme, where there is
On Fri, 7 Aug 2020 13:59:42 +0200
Cornelia Huck wrote:
> On Wed, 05 Aug 2020 12:35:01 +0100
> Sean Mooney wrote:
>
> > On Wed, 2020-08-05 at 12:53 +0200, Jiri Pirko wrote:
> > > Wed, Aug 05, 2020 at 11:33:38AM CEST, yan.y.z...@intel.com wrote:
>
> (...)
On Thu, 13 Aug 2020 15:02:53 -0400
Eric Farman wrote:
> On 8/13/20 11:33 AM, Cornelia Huck wrote:
> > On Fri, 7 Aug 2020 13:59:42 +0200
> > Cornelia Huck wrote:
> >
> >> On Wed, 05 Aug 2020 12:35:01 +0100
> >> Sean Mooney wrote:
> >>
>
On Tue, 18 Aug 2020 09:55:27 +0100
Daniel P. Berrangé wrote:
> On Tue, Aug 18, 2020 at 11:24:30AM +0800, Jason Wang wrote:
> > Another point, as we discussed in another thread, it's really hard to make
> > sure the above API work for all types of devices and frameworks. So having a
> > vendor spe
On Tue, 18 Aug 2020 10:16:28 +0100
Daniel P. Berrangé wrote:
> On Tue, Aug 18, 2020 at 05:01:51PM +0800, Jason Wang wrote:
> >On 2020/8/18 下午4:55, Daniel P. Berrangé wrote:
> >
> > On Tue, Aug 18, 2020 at 11:24:30AM +0800, Jason Wang wrote:
> >
> > On 2020/8/14 下午1:16, Yan Zhao wrote:
> >
On Tue, 18 Aug 2020 10:24:33 +0100
Daniel P. Berrangé wrote:
> On Tue, Aug 18, 2020 at 11:06:17AM +0200, Cornelia Huck wrote:
> > On Tue, 18 Aug 2020 09:55:27 +0100
> > Daniel P. Berrangé wrote:
> >
> > > On Tue, Aug 18, 2020 at 11:24:30AM +0800, Jason Wang wrot
1 - 100 of 153 matches
Mail list logo