qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
	Stefan Weil <sw@weilnetz.de>, Richard Henderson <rth@twiddle.net>,
	Alexander Graf <agraf@suse.de>
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
	David Hildenbrand <dahi@linux.vnet.ibm.com>,
	qemu-devel@nongnu.org, Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH v2] target/s390x: Fix broken user mode
Date: Wed, 22 Mar 2017 10:09:28 +0100	[thread overview]
Message-ID: <f3a081cb-42ca-ff12-83ce-51ec19c3e447@redhat.com> (raw)
In-Reply-To: <d2935727-a192-878d-49fe-77d6c4f14fb1@de.ibm.com>

On 22.03.2017 10:07, Christian Borntraeger wrote:
> On 01/30/2017 02:15 PM, Stefan Weil wrote:
>> Returning NULL from get_max_cpu_model results in a SIGSEGV runtime error.
>>
>> Signed-off-by: Stefan Weil <sw@weilnetz.de>
>> ---
>>
>> v2: Re-sent as v1 was damaged by my mailer.
>>
>> This is also broken in Debian.
>>
>> In addition, there is no default CPU ("any"), so binfmt and related
>> actions currently don't work. I hacked my local installation by
>> duplicating the "qemu" cpu definition for "any", but maybe there is
>> a better solution.
> 
> applied to our tree. Do we need cc stable as well?

Yes, I think so.

Thanks!

-- 

Thanks,

David

  reply	other threads:[~2017-03-22  9:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-30 13:15 [Qemu-devel] [PATCH v2] target/s390x: Fix broken user mode Stefan Weil
2017-01-30 14:10 ` David Hildenbrand
2017-01-30 14:44   ` Peter Maydell
2017-01-30 14:42 ` David Hildenbrand
2017-03-02 19:56 ` David Hildenbrand
2017-03-16 13:28   ` David Hildenbrand
2017-03-16 14:46     ` Philippe Mathieu-Daudé
2017-03-16 14:48       ` David Hildenbrand
2017-03-22  9:07 ` Christian Borntraeger
2017-03-22  9:09   ` David Hildenbrand [this message]
2017-03-22  9:09 ` Christian Borntraeger

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=f3a081cb-42ca-ff12-83ce-51ec19c3e447@redhat.com \
    --to=david@redhat.com \
    --cc=agraf@suse.de \
    --cc=aurelien@aurel32.net \
    --cc=borntraeger@de.ibm.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=dahi@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=sw@weilnetz.de \
    /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).