From: Petre Ovidiu PIRCALABU <ppircalabu@bitdefender.com>
To: "JBeulich@suse.com" <JBeulich@suse.com>,
"Paul.Durrant@citrix.com" <Paul.Durrant@citrix.com>
Cc: "kevin.tian@intel.com" <kevin.tian@intel.com>,
"sstabellini@kernel.org" <sstabellini@kernel.org>,
"wei.liu2@citrix.com" <wei.liu2@citrix.com>,
"rcojocaru@bitdefender.com" <rcojocaru@bitdefender.com>,
"Andrew.Cooper3@citrix.com" <Andrew.Cooper3@citrix.com>,
"tim@xen.org" <tim@xen.org>,
"George.Dunlap@citrix.com" <George.Dunlap@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
"tamas@tklengyel.com" <tamas@tklengyel.com>,
"jun.nakajima@intel.com" <jun.nakajima@intel.com>,
"Ian.Jackson@citrix.com" <Ian.Jackson@citrix.com>
Subject: Re: [PATCH v12 4/4] x86emul: Raise #UD when emulating an unrecognized instruction.
Date: Mon, 25 Sep 2017 06:22:25 +0000 [thread overview]
Message-ID: <1506320517.2094.1.camel@bitdefender.com> (raw)
In-Reply-To: <59C3D057020000780017DFF2@prv-mh.provo.novell.com>
On Jo, 2017-09-21 at 06:44 -0600, Jan Beulich wrote:
> >
> > >
> > > >
> > > > On 21.09.17 at 10:57, <Paul.Durrant@citrix.com> wrote:
> > > From: Petre Pircalabu [mailto:ppircalabu@bitdefender.com]
> > > Sent: 21 September 2017 06:12
> > > --- a/xen/arch/x86/hvm/vmx/realmode.c
> > > +++ b/xen/arch/x86/hvm/vmx/realmode.c
> > > @@ -106,12 +106,21 @@ void vmx_realmode_emulate_one(struct
> > > hvm_emulate_ctxt *hvmemul_ctxt)
> > > if ( hvm_vcpu_io_need_completion(vio) || vio->mmio_retry )
> > > vio->io_completion = HVMIO_realmode_completion;
> > >
> > > - if ( rc == X86EMUL_UNHANDLEABLE || rc ==
> > > X86EMUL_UNIMPLEMENTED
> > > )
> > > + if ( rc == X86EMUL_UNHANDLEABLE )
> > I don't quite understand this change. Why has it become unnecessary
> > to deal
> > with X86EMUL_UNIMPLEMENTED? Patch #1 added this change so it seems
> > odd that
> > patch #4 would then revert it.
> Yeah, it would certainly be more natural to bring things into
> their final shape right away.
>
> Jan
>
>
> ________________________
> This email was scanned by Bitdefender
Thank-you very much for your observation.
I will squash this patch into the first patch of the series. ("x86emul:
New return code for unimplemented instruction")
//Petre
________________________
This email was scanned by Bitdefender
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-09-25 6:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 5:12 [PATCH v12 0/4] Notify monitor when emulating an unimplemented instruction Petre Pircalabu
2017-09-21 5:12 ` [PATCH v12 1/4] x86emul: New return code for " Petre Pircalabu
2017-09-21 8:53 ` Paul Durrant
2017-09-23 18:56 ` Petre Ovidiu PIRCALABU
2017-09-25 7:54 ` Paul Durrant
2017-09-21 12:42 ` Jan Beulich
2017-09-25 9:16 ` Petre Ovidiu PIRCALABU
2017-09-25 10:36 ` Jan Beulich
2017-09-22 9:10 ` Jan Beulich
2017-09-21 5:12 ` [PATCH v12 2/4] x86emul: Add return code information to error messages Petre Pircalabu
2017-09-21 5:12 ` [PATCH v12 3/4] x86/monitor: Notify monitor if an emulation fails Petre Pircalabu
2017-09-21 5:12 ` [PATCH v12 4/4] x86emul: Raise #UD when emulating an unrecognized instruction Petre Pircalabu
2017-09-21 8:57 ` Paul Durrant
2017-09-21 12:44 ` Jan Beulich
2017-09-25 6:22 ` Petre Ovidiu PIRCALABU [this message]
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=1506320517.2094.1.camel@bitdefender.com \
--to=ppircalabu@bitdefender.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=George.Dunlap@citrix.com \
--cc=Ian.Jackson@citrix.com \
--cc=JBeulich@suse.com \
--cc=Paul.Durrant@citrix.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=rcojocaru@bitdefender.com \
--cc=sstabellini@kernel.org \
--cc=tamas@tklengyel.com \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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.