From: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
To: Jan Beulich <jbeulich@suse.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: Ian.Jackson@eu.citrix.com, Keir Fraser <keir@xen.org>,
ian.campbell@citrix.com, "Suthikulpanit,
Suravee" <Suravee.Suthikulpanit@amd.com>,
"Hurwitz, Sherry" <sherry.hurwitz@amd.com>
Subject: Re: [PATCH RFC 0/4] x86/AMD: support newer hardware features
Date: Wed, 26 Mar 2014 17:35:11 -0500 [thread overview]
Message-ID: <5333561F.5050608@amd.com> (raw)
In-Reply-To: <CAAAAutAgdSJqYEjc4dtixuTS2S=PUx-L4Sy=JCQRZ57rTdoPCQ@mail.gmail.com>
>
> 1: SVM: support data breakpoint extension registers
> 2: PV: support data breakpoint extension registers
> 3: x86/AMD: support further feature masking MSRs
> 4: x86/AMD: clean up pre-canned family/revision handling for CPUID masking
>
> Patches 3 and 4 are fully tested; for patches 1 and 2 I'm lacking
> suitable hardware, and hence depend on AMD's help (and patch
> 1 is also still lacking some tools side adjustments). Patch 3, otoh,
> has a couple of questions to be answered. Overall this makes the
> whole series RFC only for now.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com <mailto:jbeulich@suse.com>>
>
Ah. I have been looking into adding support for data breakpoint
extension myself.
Wish I had seen this earlier :(
Anyway, I will test the patches and let you know how it goes..
Thanks,
-Aravind.
next prev parent reply other threads:[~2014-03-26 22:35 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <532880230200007800125450@nat28.tlf.novell.com>
2014-03-19 9:16 ` [PATCH RFC 0/4] x86/AMD: support newer hardware features Jan Beulich
2014-03-19 9:46 ` [PATCH RFC 1/4] x86/SVM: support data breakpoint extension registers Jan Beulich
2014-03-19 9:47 ` [PATCH RFC 2/4] x86/PV: " Jan Beulich
2014-03-19 9:47 ` [PATCH RFC 3/4] x86/AMD: support further feature masking MSRs Jan Beulich
[not found] ` <CAAAAutDJ3CzvGp9jWCS7=b3rQsG81+w_W7qXLKxDWB7QBU23DQ@mail.gmail.com>
2014-04-01 23:10 ` Fwd: " Aravind Gopalakrishnan
2014-04-03 22:44 ` Aravind Gopalakrishnan
2014-04-04 9:37 ` Jan Beulich
2014-04-04 16:21 ` Aravind Gopalakrishnan
2014-04-07 6:54 ` Jan Beulich
2014-04-07 8:52 ` Andrew Cooper
2014-04-07 9:14 ` Jan Beulich
2014-03-19 9:48 ` [PATCH RFC 4/4] x86/AMD: clean up pre-canned family/revision handling for CPUID masking Jan Beulich
2014-03-26 14:13 ` [PATCH v2 RFC 2/4] x86/PV: support data breakpoint extension registers Jan Beulich
2014-03-27 15:28 ` Ian Campbell
2014-03-27 16:03 ` Jan Beulich
2014-03-27 16:23 ` Ian Campbell
2014-03-27 16:44 ` Jan Beulich
2014-03-27 17:29 ` Ian Campbell
2014-03-28 8:05 ` Jan Beulich
2014-03-28 9:55 ` Ian Campbell
2014-03-28 10:43 ` Jan Beulich
2014-03-28 10:56 ` Ian Campbell
2014-03-27 16:03 ` Andrew Cooper
2014-03-27 16:37 ` Jan Beulich
2014-03-27 17:11 ` Andrew Cooper
2014-03-28 10:46 ` Jan Beulich
[not found] ` <CAAAAutAgdSJqYEjc4dtixuTS2S=PUx-L4Sy=JCQRZ57rTdoPCQ@mail.gmail.com>
2014-03-26 22:35 ` Aravind Gopalakrishnan [this message]
2014-04-01 23:10 ` [PATCH RFC 0/4] x86/AMD: support newer hardware features Aravind Gopalakrishnan
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=5333561F.5050608@amd.com \
--to=aravind.gopalakrishnan@amd.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=ian.campbell@citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=sherry.hurwitz@amd.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.