From: Marcelo Tosatti <mtosatti@redhat.com>
To: Jin Dongming <jin.dongming@np.css.fujitsu.com>
Cc: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
KVM list <kvm@vger.kernel.org>, Dean Nelson <dnelson@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Avi Kivity <avi@redhat.com>, Huang Ying <ying.huang@intel.com>
Subject: [Qemu-devel] Re: [PATCH 07/11] kvm, x86: unify sigbus handling, prep
Date: Thu, 14 Oct 2010 21:36:56 -0300 [thread overview]
Message-ID: <20101015003656.GA32272@amt.cnet> (raw)
In-Reply-To: <4CB6C427.10202@np.css.fujitsu.com>
On Thu, Oct 14, 2010 at 05:49:43PM +0900, Jin Dongming wrote:
> There are 2 similar functions to handle SIGBUS:
> sigbus_handler(int n, struct qemu_signalfd_siginfo *siginfo,
> void *ctx)
> kvm_on_sigbus(CPUState *env, siginfo_t *siginfo)
>
> The former is used when main thread receives SIGBUS via signalfd,
> while latter is used when vcpu thread receives SIGBUS.
> These 2 take different siginfo, but in both case required parameters
> are common, the code and the addr in the info.
>
> Restruct functions to take the code and the addr explicitly.
>
> Signed-off-by: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
> Tested-by: Jin Dongming <jin.dongming@np.css.fujitsu.com>
> ---
> qemu-kvm.c | 41 ++++++++++++++++++++---------------------
> 1 files changed, 20 insertions(+), 21 deletions(-)
Don't see the benefit, separate functions are cleaner.
next prev parent reply other threads:[~2010-10-15 1:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-14 8:49 [Qemu-devel] [PATCH 07/11] kvm, x86: unify sigbus handling, prep Jin Dongming
2010-10-15 0:36 ` Marcelo Tosatti [this message]
2010-10-15 1:29 ` [Qemu-devel] " Hidetoshi Seto
2010-10-15 1:46 ` Marcelo Tosatti
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=20101015003656.GA32272@amt.cnet \
--to=mtosatti@redhat.com \
--cc=avi@redhat.com \
--cc=dnelson@redhat.com \
--cc=jin.dongming@np.css.fujitsu.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=seto.hidetoshi@jp.fujitsu.com \
--cc=ying.huang@intel.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).