flight 61780 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/61780/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-arndale 8 leak-check/basis(8) fail REGR. vs. 59254
test-armhf-armhf-xl
flight 61782 xen-4.4-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/61782/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qcow2 9 debian-di-install fail REGR. vs. 60727
test-amd64-i386-x
On 12/09/2015 10:46, Bob Liu wrote:
Hi Julien,
Hi Bob,
On 09/12/2015 03:31 AM, Julien Grall wrote:
Hi all,
This is a follow-up on the previous discussion [1] related to guest using 64KB
page granularity not booting with backend using non-indirect grant.
This has been successly tested on
On 09/13/2015 08:06 PM, Julien Grall wrote:
>
>
> On 12/09/2015 10:46, Bob Liu wrote:
>> Hi Julien,
>
> Hi Bob,
>
>
>> On 09/12/2015 03:31 AM, Julien Grall wrote:
>>> Hi all,
>>>
>>> This is a follow-up on the previous discussion [1] related to guest using
>>> 64KB
>>> page granularity not b
flight 61784 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/61784/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-pvh-intel 11 guest-start fail REGR. vs. 61692
test-armhf-armhf-xl
flight 61786 linux-3.16 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/61786/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 9 debian-hvm-install fail
REGR. vs. 60836
Regre
On 13/09/2015 13:44, Bob Liu wrote:
I may misunderstood here.
But I think same changes are also required even if backend supports indirect
grant when frontend is using 64KB page granularity.
Else
1) How to set up the grant map for requests in domU?
The minimum segment buffer size in a request
flight 61789 xen-4.2-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/61789/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-localmigrate/x10 fail REGR. vs.
60704
test-amd64-
flight 61790 xen-4.3-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/61790/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-raw 9 debian-di-install fail REGR. vs. 60742
Regressions which
On 09/14/2015 01:47 AM, Julien Grall wrote:
>
>
> On 13/09/2015 13:44, Bob Liu wrote:
>> I may misunderstood here.
>> But I think same changes are also required even if backend supports indirect
>> grant when frontend is using 64KB page granularity.
>> Else
>> 1) How to set up the grant map fo
We change to NULL the cpufreq_cpu_policy pointer after the call of
cpufreq_driver->exit, because the pointer is still needed in
intel_pstate_set_pstate().
Signed-off-by: Wei Wang
---
xen/drivers/cpufreq/cpufreq.c | 6 +++---
xen/include/acpi/cpufreq/cpufreq.h | 7 +++
2 files changed, 1
Add support to detect the APERF/MPERF feature. Also, remove the identical
code in cpufreq.c and powernow.c. This patch is independent of the
earlier patches.
Signed-off-by: Wei Wang
---
xen/arch/x86/acpi/cpufreq/cpufreq.c | 6 ++
xen/arch/x86/acpi/cpufreq/powernow.c | 6 ++
xen/arch/x86
The intel_pstate driver receives percentage values to set the
performance limits. This patch adds interfaces to support the
input of percentage values to control the intel_pstate driver.
The "get-cpufreq-para" is modified to show percentage
based feedback info.
Also, some changes in identation are
Move the driver register function to
the cpufreq.c.
Signed-off-by: Wei Wang
---
xen/drivers/cpufreq/cpufreq.c | 15 +++
xen/include/acpi/cpufreq/cpufreq.h | 27 +--
2 files changed, 16 insertions(+), 26 deletions(-)
changes in v5:
1) keep cpufreq_presm
In order to better support future Intel processors, intel_pstate
changes to use percentage values to tune P-states. The setpolicy
driver interface is used to configure the intel_pstate internal
policy. The __cpufreq_set_policy needs to be intercepted to use
the setpolicy driver if it exists.
Signe
v5 changes:
We have made various changes in this version, including introducing new
data structures, coding styles changes etc. Please see each patch's commit
message for change details.
v4 changes:
1) introduce a new struct, internal_governor, to "cpufreq_policy";
2) add a new header file, xen/in
The added calculation related functions will be used in the intel_pstate.c.
They are copied from the Linux kernel(commit 2418f4f2, f3002134, eb18cba7).
Signed-off-by: Wei Wang
---
xen/arch/x86/oprofile/op_model_athlon.c | 9
xen/include/asm-x86/div64.h | 79
By default, the old P-state driver (acpi-freq) is used. Adding
"intel_pstate" to the Xen booting param list to enable the
use of intel_pstate. However, if intel_pstate is enabled on a
machine which does not support the driver (e.g. Nehalem), the
old P-state driver will be loaded due to the failure
We simply grab the fundamental logic of the intel_pstate driver
from Linux kernel, and customize it to Xen style. In the kernel,
a user can adjust the limits via sysfs
(limits.min_sysfs_pct/max_sysfs_pct). In Xen, the
policy->limits.min_perf_pct/max_perf_pct acts as the transit
station. A user inte
Add support in the pmstat.c so that the xenpm tool can request to
access the intel_pstate driver.
Signed-off-by: Wei Wang
---
tools/libxc/xc_pm.c | 15 ++--
xen/drivers/acpi/pmstat.c | 179 +---
xen/include/public/sysctl.h | 29 ---
3 files
By default, the old P-state driver (acpi-freq) is used. Adding
"intel_pstate" to the Xen booting param list to enable the
use of intel_pstate. However, if intel_pstate is enabled on a
machine which does not support the driver (e.g. Nehalem), the
old P-state driver will be loaded due to the failure
CDP extends CAT and provides the capacity to control L3 code & data
cache. With CDP, one COS correspond to two CMBs(code & data). cbm_type
is added to support distinguish different CBM operation. Besides, new
domctl cmds are introdunced to support set/get CDP CBM. Some CAT
functions to operation CB
Changes in v3:
- x86: remove redundant CDP field in cat_socket_enable (suggested by Chao)
- tools: simplify CBM setting function in tools (suggested by Jan)
- docs: Add boot parameter description (suggested by Chao & Ian)
- code style
Changes in v2:
- x86: Enable CDP by boot parameter instead of
Add boot parameter `psr=cdp` to enable CDP at boot time.
Intel Code/Data Prioritization(CDP) feature is based on CAT. Note that
cos_max would be half when CDP is on. struct psr_cat_cbm is extended to
support CDP operation. Extend psr_get_cat_l3_info sysctl to get CDP
status.
Signed-off-by: He Chen
This is the xl/xc changes to support Intel Code/Data Prioritization.
CAT xl commands to set/get CBMs are extended to support CDP.
Signed-off-by: He Chen
---
tools/libxc/include/xenctrl.h | 7 +--
tools/libxc/xc_psr.c | 17 ++-
tools/libxl/libxl.h | 1 +
tools
Add new CDP option with CAT commands in xl interface man page.
Add description of CDP in xl-psr.markdown.
Signed-off-by: He Chen
---
docs/man/xl.pod.1 | 14 ++
docs/misc/xl-psr.markdown | 42 +-
2 files changed, 51 insertions(+), 5 dele
On 09/11/2015 04:41 PM, Ian Campbell wrote:
On Fri, 2015-09-11 at 16:18 +0200, Juergen Gross wrote:
On 09/11/2015 04:09 PM, Ian Campbell wrote:
On Fri, 2015-09-11 at 15:55 +0200, Juergen Gross wrote:
On 09/11/2015 03:26 PM, Ian Campbell wrote:
On Thu, 2015-09-10 at 23:42 -0600, Chun Yan Liu w
flight 61798 linux-3.10 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/61798/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qcow2 9 debian-di-install fail REGR. vs. 60670
test-amd64-i386-xl-vhd
flight 61799 qemu-upstream-4.4-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/61799/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-vhd9 debian-di-install fail REGR. vs. 60565
Tests w
OK, that explanation is fine to me as long as it's made clear no
security guarantee once admin uses 'relax' for any domain. Tiejun
could you resend patch with right warning/error type?
Sure, but a little bit makes me confused when I'm trying to address
this. Actually most messages are same, ex
Hi all,
I've been playing with vTPMs without any issue. I used to boot guests by
providing the kernel from dom0. Then I wanted to boot my guests using
pv-grub. Pv-grub succeeds connecting to the vTPM, however, PCRs are not
extended. The only PCR reflecting measurements is PCR10 (IMA).
vTPMs
31 matches
Mail list logo
