From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Razvan Cojocaru <rcojocaru@bitdefender.com>,
Tamas K Lengyel <tlengyel@novetta.com>,
xen-devel@lists.xenproject.org
Cc: Keir Fraser <keir@xen.org>, Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH] vm_event: Record FS_BASE/GS_BASE during events
Date: Thu, 11 Feb 2016 19:55:07 +0000 [thread overview]
Message-ID: <56BCE71B.1090003@citrix.com> (raw)
In-Reply-To: <56BCE6EA.5070501@bitdefender.com>
On 11/02/16 19:54, Razvan Cojocaru wrote:
> On 02/11/2016 09:51 PM, Tamas K Lengyel wrote:
>> While the public vm_event header specifies fs_base/gs_base as registers that
>> should be recorded for each event, that hasn't actually been the case. In
>> this patch we remedy the issue.
>>
>> Signed-off-by: Tamas K Lengyel <tlengyel@novetta.com>
>> Cc: Razvan Cojocaru <rcojocaru@bitdefender.com>
>> Cc: Keir Fraser <keir@xen.org>
>> Cc: Jan Beulich <jbeulich@suse.com>
>> Cc: Andrew Cooper <andrew.cooper3@citrix.com>
>> ---
>> xen/arch/x86/hvm/event.c | 9 ++++++++-
>> 1 file changed, 8 insertions(+), 1 deletion(-)
> Fair enough.
>
> Acked-by: Razvan Cojocaru <rcojocaru@bitdefender.com>
Oops.
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
next prev parent reply other threads:[~2016-02-11 19:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 19:51 [PATCH] vm_event: Record FS_BASE/GS_BASE during events Tamas K Lengyel
2016-02-11 19:54 ` Razvan Cojocaru
2016-02-11 19:55 ` Andrew Cooper [this message]
2016-02-11 20:00 ` Razvan Cojocaru
2016-02-11 20:04 ` Andrew Cooper
2016-02-11 20:13 ` Razvan Cojocaru
2016-02-11 20:38 ` Tamas K Lengyel
2016-02-11 20:59 ` Razvan Cojocaru
2016-02-11 21:11 ` Tamas K Lengyel
2016-02-11 21:12 ` Tamas K Lengyel
2016-02-11 21:34 ` Razvan Cojocaru
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=56BCE71B.1090003@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=rcojocaru@bitdefender.com \
--cc=tlengyel@novetta.com \
--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 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.