From: "Jan Beulich" <JBeulich@suse.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: kevin.tian@intel.com, Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Jun Nakajima <jun.nakajima@intel.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
eddie.dong@intel.com, Aravind.Gopalakrishnan@amd.com,
suravee.suthikulpanit@amd.com,
Tamas Lengyel <tamas.lengyel@zentific.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v2 1/2] x86/mem_event: Deliver gla fault EPT violation information
Date: Fri, 08 Aug 2014 15:58:19 +0100 [thread overview]
Message-ID: <53E501AB020000780002AA9F@mail.emea.novell.com> (raw)
In-Reply-To: <53E4DD34.1060804@oracle.com>
>>> On 08.08.14 at 16:22, <boris.ostrovsky@oracle.com> wrote:
> (I am also curious why we are truncating exitinfo1 to 32 bits and yet
> compiler doesn't warn.)
The compiler by default never warns about value truncations - there'd
be way too many false positives.
Jan
next prev parent reply other threads:[~2014-08-08 14:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 19:47 [PATCH v2 1/2] x86/mem_event: Deliver gla fault EPT violation information Tamas K Lengyel
2014-08-07 19:47 ` [PATCH v2 2/2] tools/xen-access: Print gla valid/fault information Tamas K Lengyel
2014-08-07 21:39 ` [PATCH v2 1/2] x86/mem_event: Deliver gla fault EPT violation information Boris Ostrovsky
2014-08-07 21:53 ` Tamas Lengyel
2014-08-07 22:58 ` Andrew Cooper
2014-08-07 23:03 ` Tamas Lengyel
2014-08-07 23:05 ` Andrew Cooper
2014-08-08 14:22 ` Boris Ostrovsky
2014-08-08 14:58 ` Jan Beulich [this message]
2014-08-08 17:47 ` Tamas Lengyel
2014-08-07 22:00 ` Andrew Cooper
2014-08-07 22:19 ` Tamas Lengyel
2014-08-07 22:54 ` Andrew Cooper
2014-08-07 22:53 ` Tian, Kevin
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=53E501AB020000780002AA9F@mail.emea.novell.com \
--to=jbeulich@suse.com \
--cc=Aravind.Gopalakrishnan@amd.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=eddie.dong@intel.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=tamas.lengyel@zentific.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 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).