From: Cornelia Huck <cohuck@redhat.com>
To: Eric Farman <farman@linux.vnet.ibm.com>
Cc: Farhan Ali <alifm@linux.vnet.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Halil Pasic <pasic@linux.vnet.ibm.com>,
walling@linux.vnet.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] s390-ccw: Fix alignment for CCW1
Date: Wed, 30 Aug 2017 09:27:57 +0200 [thread overview]
Message-ID: <20170830092757.5715a37f.cohuck@redhat.com> (raw)
In-Reply-To: <f2aaa9ff-d98a-b8fe-aff8-f5d931e10643@linux.vnet.ibm.com>
On Tue, 29 Aug 2017 14:45:51 -0400
Eric Farman <farman@linux.vnet.ibm.com> wrote:
> There were multiple $QEMUSRC directories on this system. At least one
> 2.9.xx version didn't have commit 198c0d1f9df8c4 (and thus wouldn't care
> about the boundary alignment), while others did. The aligned(8) fix
> described here was not applied universally, resulting in, uh,
> inconsistent results. Shared systems are fun. :)
>
> After a little cleanup, the results from that system match what the rest
> of us have seen/expected.
Thanks a lot for figuring that one out! I'll queue a bios update as
well.
next prev parent reply other threads:[~2017-08-30 7:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1503667215.git.alifm@linux.vnet.ibm.com>
2017-08-25 13:24 ` [Qemu-devel] [PATCH] s390-ccw: Fix alignment for CCW1 Farhan Ali
2017-08-25 13:55 ` no-reply
2017-08-25 14:04 ` Cornelia Huck
2017-08-25 15:05 ` Farhan Ali
2017-08-28 8:22 ` Cornelia Huck
2017-08-28 12:56 ` Farhan Ali
2017-08-28 13:06 ` Cornelia Huck
2017-08-28 13:18 ` Farhan Ali
2017-08-28 13:24 ` Christian Borntraeger
2017-08-28 13:52 ` Farhan Ali
2017-08-28 14:05 ` Cornelia Huck
2017-08-28 14:15 ` Farhan Ali
2017-08-28 14:19 ` Halil Pasic
2017-08-28 14:28 ` Farhan Ali
2017-08-29 12:04 ` Cornelia Huck
2017-08-29 12:39 ` Farhan Ali
2017-08-29 12:45 ` Cornelia Huck
2017-08-29 18:45 ` Eric Farman
2017-08-30 7:27 ` Cornelia Huck [this message]
2017-08-28 15:04 ` Philippe Mathieu-Daudé
2017-08-28 18:47 ` Farhan Ali
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=20170830092757.5715a37f.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=alifm@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=farman@linux.vnet.ibm.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=walling@linux.vnet.ibm.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 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).