qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Farhan Ali <alifm@linux.vnet.ibm.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Thomas Huth <thuth@redhat.com>,
	David Hildenbrand <david@redhat.com>,
	Cornelia Huck <cohuck@redhat.com>,
	Halil Pasic <pasic@linux.vnet.ibm.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	"Collin L. Walling" <walling@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] S390 bios breaks in qemu 2.10.rc3
Date: Thu, 24 Aug 2017 13:38:36 -0400	[thread overview]
Message-ID: <e24316e0-3b6f-ef1c-7c4b-66e7b302e5b4@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAFEAcA-oE=E3ydugLdVnPS2Tquqkou=BEhsB_DALqZxbVD0GDA@mail.gmail.com>



On 08/24/2017 12:07 PM, Peter Maydell wrote:
> On 24 August 2017 at 16:53, Farhan Ali <alifm@linux.vnet.ibm.com> wrote:
>>
>>
>> On 08/24/2017 11:50 AM, Thomas Huth wrote:
>>> True, so that could still be an issue. Looking at the cio.h in the
>>> kernel, they define the struct like this:
>>>
>>> struct ccw1 {
>>>         __u8  cmd_code;
>>>         __u8  flags;
>>>         __u16 count;
>>>         __u32 cda;
>>> } __attribute__ ((packed,aligned(8)));
>>>
>>> So I guess adding the aligned(8) is the right way to go?
>
>> This was my initial fix and it works on my system. But for some reason this
>> fix does not work on my colleague's system. So I am hesitant about
>> submitting this fix
>
> It seems like it ought to be the obvious fix, so I would double
> check that on your colleague's system the change really did
> get recompiled and it's actually using the new version (that
> sort of mistake can be easy to make and very confusing...)
>
> thanks
> -- PMM
>

So after trying again with the fix, it seems to work on my colleague's 
system for most cases. It fails for LDL DASD boot case.... we are still 
investigating it.

  reply	other threads:[~2017-08-24 17:38 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-24 15:05 [Qemu-devel] S390 bios breaks in qemu 2.10.rc3 Farhan Ali
2017-08-24 15:13 ` Cornelia Huck
2017-08-24 15:35   ` Thomas Huth
2017-08-24 15:47     ` Halil Pasic
2017-08-24 15:50       ` Thomas Huth
2017-08-24 15:53         ` Farhan Ali
2017-08-24 16:02           ` Halil Pasic
2017-08-24 18:15             ` Christian Borntraeger
2017-08-24 16:07           ` Peter Maydell
2017-08-24 17:38             ` Farhan Ali [this message]
2017-08-24 18:14               ` Christian Borntraeger
2017-08-25  7:20                 ` Cornelia Huck
2017-08-25  8:21                   ` Christian Borntraeger
2017-08-25  8:29                     ` Cornelia Huck
2017-08-28  7:18                       ` Christian Borntraeger
2017-08-29  9:35                         ` Thomas Huth
2017-08-29 10:28                           ` Christian Borntraeger
2017-08-31 17:44                           ` Michael Roth
2017-09-01  7:06                             ` Christian Ehrhardt
2017-09-01 14:03                               ` Michael Roth
2017-08-25 14:38                   ` Philippe Mathieu-Daudé
2017-08-24 15:37   ` Halil Pasic
2017-08-24 18:33 ` Christian Borntraeger
2017-08-24 19:56   ` 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=e24316e0-3b6f-ef1c-7c4b-66e7b302e5b4@linux.vnet.ibm.com \
    --to=alifm@linux.vnet.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=pasic@linux.vnet.ibm.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    --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).