From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: imammedo@redhat.com, ehabkost@redhat.com, dgilbert@redhat.com
Subject: [Qemu-devel] [PATCH 0/2] cpu->exception_index fixes
Date: Fri, 19 Dec 2014 12:53:12 +0100 [thread overview]
Message-ID: <1418989994-17244-1-git-send-email-pbonzini@redhat.com> (raw)
Two fixes for cpu->exception_index:
- breakage of linux-user from commit e511b4d
- wrong subsection definition in 2.2 (see patch 2)
Paolo
Paolo Bonzini (2):
cpu: initialize cpu->exception_index on reset
exec: change default exception_index value for migration to -1
cpus.c | 3 ---
exec.c | 4 ++--
qom/cpu.c | 1 +
3 files changed, 3 insertions(+), 5 deletions(-)
--
1.8.3.1
next reply other threads:[~2014-12-19 11:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 11:53 Paolo Bonzini [this message]
2014-12-19 11:53 ` [Qemu-devel] [PATCH 1/2] cpu: initialize cpu->exception_index on reset Paolo Bonzini
2014-12-19 13:29 ` Eduardo Habkost
2014-12-19 11:53 ` [Qemu-devel] [PATCH 2/2] exec: change default exception_index value for migration to -1 Paolo Bonzini
2014-12-19 12:25 ` [Qemu-devel] [PATCH 0/2] cpu->exception_index fixes Laurent Desnogues
2014-12-20 21:28 ` Peter Maydell
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=1418989994-17244-1-git-send-email-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.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 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).