All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Aurelien Jarno <aurelien@aurel32.net>, Alexander Graf <agraf@suse.de>
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] s390x: Switch to s390-ccw machine as default
Date: Thu, 18 Jun 2015 16:57:52 +0200	[thread overview]
Message-ID: <5582DC70.8060709@de.ibm.com> (raw)
In-Reply-To: <20150616212326.GB17031@aurel32.net>

Am 16.06.2015 um 23:23 schrieb Aurelien Jarno:
> On 2015-06-16 23:08, Alexander Graf wrote:
>> We now finally have TCG support for the basic set of instructions necessary
>> to run the s390-ccw machine. That means in any aspect possible that machine
>> type is now superior to the legacy s390-virtio machine.
>>
>> Switch over to the ccw machine as default. That way people don't get a halfway
>> broken machine with the s390x target.
>>
>> Signed-off-by: Alexander Graf <agraf@suse.de>
> 
> \o/ Very good idea!
> 
> Reviewed-by: Aurelien Jarno <aurelien@aurel32.net>
> 
> That said in the future it would be even better if we can automagically
> pass bootindex=1 to the first created drive when not declaring the
> device and the drive separately. That would allow to run an image with
> just:

This is actually a bug that was introduced with 
commit fa92e218df1d ("s390x/ipl: avoid sign extension")
Will prepare a fix.

Christian

  reply	other threads:[~2015-06-18 14:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-16 21:08 [Qemu-devel] [PATCH] s390x: Switch to s390-ccw machine as default Alexander Graf
2015-06-16 21:23 ` Aurelien Jarno
2015-06-18 14:57   ` Christian Borntraeger [this message]
2015-06-16 21:27 ` Christian Borntraeger
2015-06-17 13:46 ` Aurelien Jarno
2015-06-17 14:00   ` Christian Borntraeger
2015-06-17 14:32     ` Aurelien Jarno

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=5582DC70.8060709@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=agraf@suse.de \
    --cc=aurelien@aurel32.net \
    --cc=cornelia.huck@de.ibm.com \
    --cc=qemu-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.