From: Alexandru Stefan ISAILA <aisaila@bitdefender.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Wei Liu <wl@xen.org>,
"kevin.tian@intel.com" <kevin.tian@intel.com>,
"tamas@tklengyel.com" <tamas@tklengyel.com>,
"jun.nakajima@intel.com" <jun.nakajima@intel.com>,
"rcojocaru@bitdefender.com" <rcojocaru@bitdefender.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Tim Deegan <tim@xen.org>, PaulDurrant <Paul.Durrant@citrix.com>,
"suravee.suthikulpanit@amd.com" <suravee.suthikulpanit@amd.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
"brian.woods@amd.com" <brian.woods@amd.com>,
Roger PauMonne <roger.pau@citrix.com>
Subject: Re: [Xen-devel] [PATCH v5] x86/emulate: Send vm_event from emulate
Date: Tue, 2 Jul 2019 07:58:04 +0000 [thread overview]
Message-ID: <23adc806-181b-8190-06ed-84e654628424@bitdefender.com> (raw)
In-Reply-To: <031156bc-936f-79e0-e1ca-3e49a1274c71@suse.com>
On 01.07.2019 18:53, Jan Beulich wrote:
> On 01.07.2019 17:36, Alexandru Stefan ISAILA wrote:
>> On 01.07.2019 17:55, Jan Beulich wrote:
>>> On 01.07.2019 16:45, Alexandru Stefan ISAILA wrote:
>>>> On 01.07.2019 16:13, Jan Beulich wrote:
>>>>>>>> On 04.06.19 at 13:49, <aisaila@bitdefender.com> wrote:
>>>>>> + if ( !req.u.mem_access.flags )
>>>>>> + return false; /* no violation */
>>>>>
>>>>> How is the "false" here (I think this is the one the description talks
>>>>> about) matching up with the various other ones in the function?
>>>>
>>>> There should be no event if there is no access violation. So in this
>>>> case the emulation is continued as expected.
>>>
>>> But this doesn't answer my question: You use "false" as return value
>>> to indicate different things. Only the one here means "no access
>>> violation".
>>
>> Sorry about that, since this will remain the only return false apart
>> form the main one (return monitor_traps()), false = event was not sent
>> and true = event was sent.
>>
>> I understand that you are asking about the scenario when there was a
>> violation and the event was not sent. Then I can issue a domain_crash()
>> as that is potentially a big issue.
>>
>> I hope I got that correctly.
>
> I don't get the impression that you did. I count a total of four
> "return false" in the function, only one of which explicitly means
> "no access violation" (others may have that meaning implicitly). Let's
> take the p2m_get_mem_access() failure case as an example: What I don't
> understand is why this case and the "no access violation" one are both
> meant to be treated the same.
Right, at the moment, false means that emulation should continue and
true means that emulation should stop. If it is a must that I return
different errors I will change that in the next version but in the way
that the code is right now they will be treated the same way.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-07-02 7:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 13:13 [Xen-devel] [PATCH v5] x86/emulate: Send vm_event from emulate Jan Beulich
2019-07-01 14:45 ` Alexandru Stefan ISAILA
2019-07-01 14:55 ` Jan Beulich
2019-07-01 15:36 ` Alexandru Stefan ISAILA
2019-07-01 15:53 ` Jan Beulich
2019-07-02 7:58 ` Alexandru Stefan ISAILA [this message]
2019-07-02 8:01 ` Jan Beulich
2019-07-02 8:10 ` Alexandru Stefan ISAILA
2019-07-01 15:13 ` Razvan Cojocaru
2019-07-01 15:32 ` Jan Beulich
-- strict thread matches above, loose matches on Subject: below --
2019-06-04 11:49 Alexandru Stefan ISAILA
2019-06-11 12:45 ` Paul Durrant
2019-06-12 9:27 ` Alexandru Stefan ISAILA
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=23adc806-181b-8190-06ed-84e654628424@bitdefender.com \
--to=aisaila@bitdefender.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=Paul.Durrant@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=brian.woods@amd.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=rcojocaru@bitdefender.com \
--cc=roger.pau@citrix.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=tamas@tklengyel.com \
--cc=tim@xen.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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).