This patch adds pkeys support for cpuid handing.
Pkeys hardware support is CPUID.7.0.ECX[3]:PKU. software support is
CPUID.7.0.ECX[4]:OSPKE and it reflects the support setting of CR4.PKE.
Signed-off-by: Huaitong Han
---
tools/libxc/xc_cpufeature.h | 2 ++
tools/libxc/xc_cpuid_x86.c | 6 -
This patch adds xstate support for pkeys.
Signed-off-by: Huaitong Han
Reviewed-by: Andrew Cooper
---
xen/include/asm-x86/xstate.h | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/xen/include/asm-x86/xstate.h b/xen/include/asm-x86/xstate.h
index 12d939b..f7c41ba 100644
---
Changes in v4:
*Delete gva2gfn patch, and when page is present, PFEC_prot_key is always
checked.
*Use RDPKRU instead of xsave_read because RDPKRU does cost less.
*Squash pkeys patch and pkru patch to guest_walk_tables patch.
Changes in v3:
*Get CPUID:ospke depend on guest cpuid instead of host ha
Protection keys define a new 4-bit protection key field(PKEY) in bits 62:59 of
leaf entries of the page tables.
PKRU register defines 32 bits, there are 16 domains and 2 attribute bits per
domain in pkru, for each i (0 ≤ i ≤ 15), PKRU[2i] is the access-disable bit for
protection key i (ADi); PKRU[
This patch disables pkeys for guest in non-paging mode, However XEN always uses
paging mode to emulate guest non-paging mode, To emulate this behavior, pkeys
needs to be manually disabled when guest switches to non-paging mode.
Signed-off-by: Huaitong Han
Reviewed-by: Andrew Cooper
---
xen/arch
This patch adds pkeys support when setting CR4.
Signed-off-by: Huaitong Han
Reviewed-by: Andrew Cooper
---
xen/arch/x86/hvm/hvm.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/xen/arch/x86/hvm/hvm.c b/xen/arch/x86/hvm/hvm.c
index db0aeba..59916ed 100644
--- a/xen/arch/
On some architectures smp_store_mb() calls mb() which is stronger
than implied by both the name and the documentation.
smp_store_mb is only used by core kernel code at the moment, so
we know no one mis-uses it for an MMIO barrier.
Make it call smp_mb consistently before some arch-specific
code use
This patch adds the flag to enable Memory Protection Keys.
Signed-off-by: Huaitong Han
Reviewed-by: Andrew Cooper
---
docs/misc/xen-command-line.markdown | 10 ++
xen/arch/x86/cpu/common.c | 10 +-
xen/include/asm-x86/cpufeature.h| 6 +-
3 files changed, 24 in
On Sun, Dec 20, 2015 at 08:59:44PM +0100, Peter Zijlstra wrote:
> On Sun, Dec 20, 2015 at 05:07:19PM +, Andrew Cooper wrote:
> >
> > Very much +1 for fixing this.
> >
> > Those names would be fine, but they do add yet another set of options in
> > an already-complicated area.
> >
> > An alte
Ping...
> -Original Message-
> From: Wu, Feng
> Sent: Thursday, December 3, 2015 4:36 PM
> To: xen-devel@lists.xen.org
> Cc: Wu, Feng ; Keir Fraser ; Jan Beulich
> ; Andrew Cooper ; Tian,
> Kevin ; George Dunlap ;
> Dario Faggioli
> Subject: [PATCH v10 6/7] vmx: VT-d posted-interrupt core
flight 66671 linux-mingo-tip-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/66671/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-pvops 5 kernel-build fail REGR. vs. 60684
build-amd6
flight 66638 xen-4.3-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/66638/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 5 xen-build fail REGR. vs. 65650
build-amd64-prev
Refer to SDM 13.4.3. The value return by ecx[1] with cpuid
function 0xdh and sub-fucntion i (i>1) indicates the alignment
of the state component i when the compacted format of the extended
region of an xsave area is used.
So when hvm guest using CPUID eax=0xdh,ecx=1 to get the size of area
used fo
flight 66631 qemu-upstream-4.6-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/66631/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 63071
test-am
flight 66639 qemu-upstream-4.4-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/66639/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 62702
test-am
flight 66622 qemu-upstream-4.5-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/66622/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 62414
test-am
On Sun, Dec 20, 2015 at 05:07:19PM +, Andrew Cooper wrote:
>
> Very much +1 for fixing this.
>
> Those names would be fine, but they do add yet another set of options in
> an already-complicated area.
>
> An alternative might be to have the regular smp_{w,r,}mb() not revert
> back to nops if
flight 66614 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/66614/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemut-winxpsp3 6 xen-boot fail REGR. vs. 59254
test-amd64-i386-freeb
On 12/16/15 10:12, Jan Beulich wrote:
On 28.11.15 at 22:45, wrote:
>> ---
>> v13:
>> Changed to uint32_t arch_flags, since the emulation_flags is this.
>
> I don't really understand this sentence, and I also don't understand
> why you couldn't just use another XEN_X86_EMU_ flag, e.g.
> XEN
On 12/16/15 05:28, Jan Beulich wrote:
On 28.11.15 at 22:44, wrote:
>> --- a/xen/include/public/arch-x86/xen.h
>> +++ b/xen/include/public/arch-x86/xen.h
>> @@ -290,6 +290,7 @@ struct xen_arch_domainconfig {
>> XEN_X86_EMU_VGA | XEN_X86_EMU_IOMMU |
>> \
On 20/12/15 09:25, Michael S. Tsirkin wrote:
> On Thu, Dec 17, 2015 at 03:39:10PM +0100, Peter Zijlstra wrote:
>> On Thu, Dec 17, 2015 at 04:33:44PM +0200, Michael S. Tsirkin wrote:
>>> On Thu, Dec 17, 2015 at 02:57:26PM +0100, Peter Zijlstra wrote:
You could of course go fix that instead of m
flight 66615 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/66615/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm5 xen-build fail REGR. vs. 66433
build-amd64
xen/tools/get-fields.sh used echo -n which is not POSIX compatible and
breaks building with dash (shell). Change it to use printf '%s' which
is usable everywhere.
Signed-off-by: Alex Xu
---
xen/tools/get-fields.sh | 30 +++---
1 file changed, 15 insertions(+), 15 deletion
flight 66590 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/66590/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3865 xen-build fail REGR. vs. 66415
build-i386-xsm
On 20/12/15 13:57, Xu, Quan wrote:
>> On 12.12.2015 at 9:22pm, wrote:
>> This patches are based on Kevin Tian's previous discussion 'Revisit
>> VT-d asynchronous flush issue'.
>> Fix current timeout concern and also allow limited ATS support in a light
>> way:
>
>> 2. Fix vt-d flush timeout iss
On 20/12/15 13:42, Doug Goldstein wrote:
> On 12/18/15 4:09 PM, Andrew Cooper wrote:
>> On 18/12/2015 21:49, Doug Goldstein wrote:
>>> On 12/18/15 3:35 PM, Andrew Cooper wrote:
On 18/12/2015 20:06, Doug Goldstein wrote:
> Use the Kconfig generated CONFIG_COMPAT defines in the code base.
>>
flight 66587 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/66587/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd64 17 guest-start/debianhvm.repeat fail
REGR. vs. 65543
test-amd64-i386-
>On 12.12.2015 at 9:22pm, wrote:
> This patches are based on Kevin Tian's previous discussion 'Revisit
>VT-d asynchronous flush issue'.
> Fix current timeout concern and also allow limited ATS support in a light way:
> 2. Fix vt-d flush timeout issue.
>
> If IOTLB/Context/IETC flush is t
flight 66602 qemu-upstream-4.3-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/66602/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3865 xen-build fail REGR. vs. 62112
build-a
On 12/18/15 4:09 PM, Andrew Cooper wrote:
> On 18/12/2015 21:49, Doug Goldstein wrote:
>> On 12/18/15 3:35 PM, Andrew Cooper wrote:
>>> On 18/12/2015 20:06, Doug Goldstein wrote:
Use the Kconfig generated CONFIG_COMPAT defines in the code base.
CC: Keir Fraser
CC: Jan Beulich
flight 66604 qemu-upstream-4.2-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/66604/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3865 xen-build fail REGR. vs. 62044
build-a
branch xen-unstable
xenbranch xen-unstable
job build-i386
testid xen-build
Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
Tree: qemuu git://xenbits.xen.org/qemu-xen.git
Tree: xen git://xenbits.xen.org/xen.git
*** Found and reproduced problem changeset ***
Bug is in tree: xen git://
flight 66583 xen-4.4-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/66583/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-prev 5 xen-build fail REGR. vs. 66458
build-i386-prev
flight 66579 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/66579/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-libvirt-vhd 9 debian-di-installfail like 66498
Tests which did not succeed, but a
On Thu, Dec 17, 2015 at 03:39:10PM +0100, Peter Zijlstra wrote:
> On Thu, Dec 17, 2015 at 04:33:44PM +0200, Michael S. Tsirkin wrote:
> > On Thu, Dec 17, 2015 at 02:57:26PM +0100, Peter Zijlstra wrote:
> > >
> > > You could of course go fix that instead of mutilating things into
> > > sort-of func
flight 66574 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/66574/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-rumpuserxen-i386 10 guest-start fail REGR. vs. 63732
Regressions which are
36 matches
Mail list logo
