search for: kaod

...> >> Reported-by: Michael A. Tebolt <miket at us.ibm.com> >> Reported-by: Dr. David Alan Gilbert <dgilbert at redhat.com> >> Fixes: commit 2751c9882b94 ("vhost: cross-endian support for legacy devices") >> --- > Reviewed-by: Greg Kurz <groug at kaod.org> > Thanks! We have some tests on s390x (that is BE) running, but I won't be able to test the change with cross endian and legacy. What do you think, should I/we RFT or are we fine without? Regards, Halil

...> >> Reported-by: Michael A. Tebolt <miket at us.ibm.com> >> Reported-by: Dr. David Alan Gilbert <dgilbert at redhat.com> >> Fixes: commit 2751c9882b94 ("vhost: cross-endian support for legacy devices") >> --- > Reviewed-by: Greg Kurz <groug at kaod.org> > Thanks! We have some tests on s390x (that is BE) running, but I won't be able to test the change with cross endian and legacy. What do you think, should I/we RFT or are we fine without? Regards, Halil

Currently, under certain circumstances vhost_init_is_le does just a part of the initialization job, and depends on vhost_reset_is_le being called too. For this reason vhost_vq_init_access used to call vhost_reset_is_le when vq->private_data is NULL. This is not only counter intuitive, but also real a problem because it breaks vhost_net. The bug was introduced to vhost_net with commit

Currently, under certain circumstances vhost_init_is_le does just a part of the initialization job, and depends on vhost_reset_is_le being called too. For this reason vhost_vq_init_access used to call vhost_reset_is_le when vq->private_data is NULL. This is not only counter intuitive, but also real a problem because it breaks vhost_net. The bug was introduced to vhost_net with commit

...t linux.vnet.ibm.com> > Reported-by: Michael A. Tebolt <miket at us.ibm.com> > Reported-by: Dr. David Alan Gilbert <dgilbert at redhat.com> > Fixes: commit 2751c9882b94 ("vhost: cross-endian support for legacy devices") > --- Reviewed-by: Greg Kurz <groug at kaod.org> > > The bug was already discussed here: > http://www.spinics.net/lists/kvm/msg144365.html > This is a follow up patch. > > --- > drivers/vhost/vhost.c | 10 ++++------ > 1 file changed, 4 insertions(+), 6 deletions(-) > > diff --git a/drivers/vhost/vhost....

...ed-by: Michael A. Tebolt <miket at us.ibm.com> > >> Reported-by: Dr. David Alan Gilbert <dgilbert at redhat.com> > >> Fixes: commit 2751c9882b94 ("vhost: cross-endian support for legacy devices") > >> --- > > Reviewed-by: Greg Kurz <groug at kaod.org> > > > > Thanks! > > We have some tests on s390x (that is BE) running, but I won't be able to > test the change with cross endian and legacy. > > What do you think, should I/we RFT or are we fine without? > > Regards, > Halil More testing can...

...e performed at IOTLB prefetch time anyway. > > BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1883084 > Fixes: 6b1e6cc7855b ("vhost: new device IOTLB API") > Cc: jasowang at redhat.com > CC: stable at vger.kernel.org # 4.14+ > Signed-off-by: Greg Kurz <groug at kaod.org> Hmm I was sure the addresses are HVAs in any case ... Jason? > --- > drivers/vhost/vhost.c | 5 ++++- > 1 file changed, 4 insertions(+), 1 deletion(-) > > diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c > index b45519ca66a7..6296e33df31d 100644 > --- a...

...e performed at IOTLB prefetch time anyway. > > BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1883084 > Fixes: 6b1e6cc7855b ("vhost: new device IOTLB API") > Cc: jasowang at redhat.com > CC: stable at vger.kernel.org # 4.14+ > Signed-off-by: Greg Kurz <groug at kaod.org> > --- > drivers/vhost/vhost.c | 5 ++++- > 1 file changed, 4 insertions(+), 1 deletion(-) > > diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c > index b45519ca66a7..6296e33df31d 100644 > --- a/drivers/vhost/vhost.c > +++ b/drivers/vhost/vhost.c > @@...

On Fri, 27 Jan 2017 13:24:13 +0100 Halil Pasic <pasic at linux.vnet.ibm.com> wrote: > On 01/26/2017 08:20 PM, Michael S. Tsirkin wrote: > > On Thu, Jan 26, 2017 at 06:39:14PM +0100, Halil Pasic wrote: > >> > >> Hi! > >> > >> Recently I have been investigating some strange migration problems on > >> s390x. > >> > >> It