>>> On 22.02.16 at 19:43, wrote:
> On 2/22/16 10:36 AM, Jan Beulich wrote:
> On 08.02.16 at 18:07, wrote:
>>> There is no reason for any of it to be modified. Additionally, link
>>> .init.setup beside the other constant .init data.
>>>
>>> No functional change.
>>>
>>> Signed-off-by: Andrew
>>> On 22.02.16 at 22:14, wrote:
(Please trim you replies.)
> Ping: Or would you prefer resubmitting with the comments so far?
Either way is fine. It's on my list of thing to look at, but being RFC
it ranges priority wise behind various other things; I've been hoping
to get to it a number of ti
hi !
I am transplanting the xen-4.7 on my OMAP5432 uEVM board,but after booting the
xen ,the dom0 kernel didnot boot successfully(no console output while booting
the dom0 kernel).I followed my step from this link:
Xen_ARM_with_Virtualization_Extensions/OMAP5432_uEVM
my u-boot command and bo
>>> On 23.02.16 at 05:59, wrote:
>
>> -Original Message-
>> From: Jan Beulich [mailto:jbeul...@suse.com]
>> Sent: Monday, February 22, 2016 9:08 PM
>> To: Wu, Feng
>> Cc: Andrew Cooper ; Dario Faggioli
>> ; George Dunlap ;
>> Tian, Kevin ; xen-devel@lists.xen.org; Keir Fraser
>>
>> Sub
Hi Jan,
I found some issues in your patch, see the comments below.
> -Original Message-
> From: xen-devel-boun...@lists.xen.org [mailto:xen-devel-
> boun...@lists.xen.org] On Behalf Of Jan Beulich
> Sent: Monday, October 19, 2015 11:23 PM
> To: xen-devel
> Cc: Tian, Kevin; Nakajima, Jun
* Luis R. Rodriguez wrote:
> Although hardware_subarch has been in place since the x86 boot
> protocol 2.07 it hasn't been used much. Enumerate current possible
> values to avoid misuses and help with semantics later at boot
> time should this be used further.
>
> v2: fix typos
>
> Cc: Andy Sh
Enable VT-d Posted-Interrupts and add a command line
parameter for it.
CC: Jan Beulich
Signed-off-by: Feng Wu
Reviewed-by: Kevin Tian
Acked-by: Jan Beulich
---
docs/misc/xen-command-line.markdown | 9 -
xen/drivers/passthrough/iommu.c | 3 +++
2 files changed, 11 insertions(+), 1
VT-d Posted-Interrupts is an enhancement to CPU side Posted-Interrupt.
With VT-d Posted-Interrupts enabled, external interrupts from
direct-assigned devices can be delivered to guests without VMM
intervention when guest is running in non-root mode.
You can find the VT-d Posted-Interrtups Spec. in
This is the core logic handling for VT-d posted-interrupts. Basically it
deals with how and when to update posted-interrupts during the following
scenarios:
- vCPU is preempted
- vCPU is slept
- vCPU is blocked
When vCPU is preempted/slept, we update the posted-interrupts during
scheduling by intr
> From: Andrew Cooper [mailto:andrew.coop...@citrix.com]
> Sent: Monday, January 11, 2016 5:59 PM
> To: Wei Liu; Li, Liang Z
> Cc: ian.campb...@citrix.com; stefano.stabell...@eu.citrix.com;
> ian.jack...@eu.citrix.com; xen-devel@lists.xen.org; jbeul...@suse.com
> Subject: Re: [Xen-devel] [PATCH] li
flight 83609 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/83609/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-armhf-armhf-xl-credit2 15 guest-start/debian.repeat fail in 83289 pass in
83609
test-amd64-i386-libvirt-qem
On 2/18/2016 9:35 PM, Corneliu ZUZU wrote:
This patch adds ARM support for guest-request monitor vm-events.
Summary of changes:
== Moved to common-side:
* XEN_DOMCTL_MONITOR_EVENT_GUEST_REQUEST handling (moved from X86
arch_monitor_domctl_event to common monitor_domctl)
* hvm_event_
>>> On 23.02.16 at 08:35, wrote:
> In flask_sysctl_scheduler_op() the test for the desired operation is
> done with the wrong constants. While the values are correct, the names
> are not. Correct the error message for the case of an unknown
> operation, too.
>
> Signed-off-by: Juergen Gross
Wou
flight 83611 seabios real [real]
http://logs.test-lab.xenproject.org/osstest/logs/83611/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop fail like 83298
Tests which did not succeed, but a
On Mon, Feb 22, 2016 at 7:03 PM, Konrad Rzeszutek Wilk
wrote:
> On Mon, Feb 22, 2016 at 06:39:26PM +, Lars Kurth wrote:
>>
>> > On 22 Feb 2016, at 18:34, Doug Goldstein wrote:
>> >
>> > On 2/22/16 11:06 AM, Ian Jackson wrote:
>> >> Doug Goldstein writes ("[PATCH] travis: add IRC notifications
>>> On 22.02.16 at 17:57, wrote:
> --- a/xen/arch/x86/alternative.c
> +++ b/xen/arch/x86/alternative.c
> @@ -38,7 +38,7 @@ static const unsigned char k8nops[] __initconst = {
> K8_NOP7,
> K8_NOP8
> };
> -static const unsigned char * const k8_nops[ASM_NOP_MAX+1] = {
> +static const unsig
On Fri, 2016-02-19 at 12:06 -0700, Jim Fehlig wrote:
> On 02/19/2016 10:23 AM, Ian Jackson wrote:
> > Jim Fehlig writes ("[PATCH 3/3] docs: add more info about target= in
> > disk config"):
> > > target= in disk config can be used to convey arbitrary
> > > configuration information to backends. Add
On 23/02/16 10:29, Jan Beulich wrote:
On 23.02.16 at 08:35, wrote:
>> In flask_sysctl_scheduler_op() the test for the desired operation is
>> done with the wrong constants. While the values are correct, the names
>> are not. Correct the error message for the case of an unknown
>> operation, t
On Mon, 2016-02-22 at 17:29 +0800, Fu Wei wrote:
> Hi Julien,
>
> On 20 February 2016 at 00:28, Julien Grall
> wrote:
> > Xen is currently crashing because of malformed compatible property for
> > the boot module. This is because the property string is not
> > null-terminated as requested by the
In flask_sysctl_scheduler_op() and sched_adjust_global() the test for
the desired operation is done with the wrong constants. While the
values are correct, the names are not.
Correct the error message for the case of an unknown operation in
flask_sysctl_scheduler_op(), too.
Signed-off-by: Juergen
On 23/02/16 09:47, Jan Beulich wrote:
On 22.02.16 at 17:57, wrote:
>> --- a/xen/arch/x86/alternative.c
>> +++ b/xen/arch/x86/alternative.c
>> @@ -38,7 +38,7 @@ static const unsigned char k8nops[] __initconst = {
>> K8_NOP7,
>> K8_NOP8
>> };
>> -static const unsigned char * const k8
On Fri, 2016-02-19 at 17:52 +, Ian Jackson wrote:
> The regex in mg-list-all-branches assumes that the BRANCHES= will
> either be a singleton entry separated from the following command by a
> hard tab or a single quoted list of space separated entries, however
> the xen-unstable-coverity line i
On Wed, 2016-02-17 at 10:34 +, Ian Campbell wrote:
> Dom0 is handled separately (via print_dom0_uptime) and the domU
> variant doesn't work for dom0 since libxl_vm_get_start_time() doesn't.
>
> Signed-off-by: Ian Campbell
Ping? (and for 2/2 "xl: NULL terminate buf when reading dom0 /proc/upt
>>> On 23.02.16 at 09:34, wrote:
> I found some issues in your patch, see the comments below.
Thanks for getting back on this.
>> --- a/xen/arch/x86/hvm/vmx/vmcs.c
>> +++ b/xen/arch/x86/hvm/vmx/vmcs.c
>> @@ -932,37 +932,36 @@ void vmx_vmcs_switch(paddr_t from, paddr
>> spin_unlock(&vmx->vmc
On Wed, 2016-02-17 at 10:39 +, Ian Campbell wrote:
> We assert that nullfd if not std{in,out,err} since that would result
> in closing one of the just dup2'd fds. For this to happen
> std{in,out,err} would have needed to be closed, at which point all
> sorts of other things could go wrong.
>
>
On Thu, 2016-02-11 at 11:20 +, Wei Liu wrote:
> On Wed, Feb 10, 2016 at 04:32:39PM +, Ian Campbell wrote:
> > It can be -1 at this point.
> >
> > CID 1055562
> > Signed-off-by: Ian Campbell
>
> Acked-by: Wei Liu
Ian, will you commit this one?
_
On Wed, 2016-02-17 at 11:02 +, Ian Campbell wrote:
> Coverity rightly points out that qmp->buffer may not be NULL
> terminated when passed to strncat.
>
> Make the actual buffer a byte bigger than QMP_RECEIVE_BUFFER_SIZE and
> always append a NULL byte.
>
> I suspect that in practice we have
>>> On 23.02.16 at 11:10, wrote:
> On 23/02/16 09:47, Jan Beulich wrote:
> On 22.02.16 at 17:57, wrote:
>>> --- a/xen/arch/x86/alternative.c
>>> +++ b/xen/arch/x86/alternative.c
>>> @@ -38,7 +38,7 @@ static const unsigned char k8nops[] __initconst = {
>>> K8_NOP7,
>>> K8_NOP8
>>> }
CID: 1055898
Signed-off-by: Ian Campbell
---
v2: Move spurious looking NULL assignment to previous patch where it
belongs.
---
tools/libxl/xl_cmdimpl.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/libxl/xl_cmdimpl.c b/tools/libxl/xl_cmdimpl.c
index 9f08f64..514f5a8 100644
--- a/
By delaying freeing the XLU_Config object until the end we miss doing
so on various success and error paths.
Instead free it as soon as the parsing is complete and ensure that
parse errors come through this path by exiting the loop early and
handling that error after the free instead of returning
On Tue, Feb 23, 2016 at 09:51:19AM +0100, Ingo Molnar wrote:
>
> * Luis R. Rodriguez wrote:
>
> > Although hardware_subarch has been in place since the x86 boot
> > protocol 2.07 it hasn't been used much. Enumerate current possible
> > values to avoid misuses and help with semantics later at boo
flight 83616 qemu-upstream-4.5-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/83616/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-armhf-armhf-xl 5 xen-installfail in 83346 pass in 83616
test-amd64-i386-libvi
On 23/02/16 10:09, Juergen Gross wrote:
> In flask_sysctl_scheduler_op() and sched_adjust_global() the test for
> the desired operation is done with the wrong constants. While the
> values are correct, the names are not.
>
> Correct the error message for the case of an unknown operation in
> flask
In retrospect there isn't much point in defering coverity until the
tree has been through a full test and it just results in potentially
longer gaps between runs with larger numbers of commits included (for
example the run on Sunday was skipped because master hadn't moved
forward since Wednesday).
> Thanks for getting back on this.
>
> >> --- a/xen/arch/x86/hvm/vmx/vmcs.c
> >> +++ b/xen/arch/x86/hvm/vmx/vmcs.c
> >> @@ -932,37 +932,36 @@ void vmx_vmcs_switch(paddr_t from, paddr
> >> spin_unlock(&vmx->vmcs_lock);
> >> }
> >>
> >> -void virtual_vmcs_enter(void *vvmcs)
> >> +void virtual_
On 02/23/2016 11:09 AM, Corneliu ZUZU wrote:
> On 2/18/2016 9:35 PM, Corneliu ZUZU wrote:
>> This patch adds ARM support for guest-request monitor vm-events.
>>
>> Summary of changes:
>> == Moved to common-side:
>>* XEN_DOMCTL_MONITOR_EVENT_GUEST_REQUEST handling (moved from X86
>>arch_
On 2/23/2016 12:54 PM, Razvan Cojocaru wrote:
On 02/23/2016 11:09 AM, Corneliu ZUZU wrote:
On 2/18/2016 9:35 PM, Corneliu ZUZU wrote:
This patch adds ARM support for guest-request monitor vm-events.
Summary of changes:
== Moved to common-side:
* XEN_DOMCTL_MONITOR_EVENT_GUEST_REQUEST handl
The x86 architecture allows either: a) the 64-bit FIP/FDP registers to
be restored (clearing FCS and FDS); or b) the 32-bit FIP/FDP and
FCS/FDS registers to be restored (clearing the upper 32-bits).
Add a per-domain field to indicate which of these options a guest
needs. The options are: 8, 4 or
The HVM parameter HVM_PARAM_X87_FIP_WIDTH to allow tools and the guest
to adjust the width of the FIP/FDP registers to be saved/restored by
the hypervisor. This is in case the hypervisor hueristics do not do
the right thing.
Add this parameter to the set saved during domain save/migrate.
Signed-
This series extends the workaround for the inability for some x86 CPUs
to fully restore the FPU exception state (64-bit FIP/FDP and FCS/FDS).
Toolstack (or the guest) may override the default behaviour to always
do a 32-bit save/restore.
Running Microsoft's Driver Verifier continues to work in a
The hardware may not write the FIP/FDP fields with a XSAVE*
instruction. e.g., with XSAVEOPT/XSAVES if the state hasn't changed
or on AMD CPUs when a floating point exception is not pending. We
need to identify this case so we can correctly apply the check for
whether to save/restore FCS/FDS.
By
On 02/23/2016 01:00 PM, Corneliu ZUZU wrote:
> On 2/23/2016 12:54 PM, Razvan Cojocaru wrote:
>> On 02/23/2016 11:09 AM, Corneliu ZUZU wrote:
>>> On 2/18/2016 9:35 PM, Corneliu ZUZU wrote:
This patch adds ARM support for guest-request monitor vm-events.
Summary of changes:
== Mov
On 23/02/16 08:34, Feng Wu wrote:
> This is the core logic handling for VT-d posted-interrupts. Basically it
> deals with how and when to update posted-interrupts during the following
> scenarios:
> - vCPU is preempted
> - vCPU is slept
> - vCPU is blocked
>
> When vCPU is preempted/slept, we upda
On 23/02/16 11:05, David Vrabel wrote:
> @@ -653,6 +657,12 @@ int arch_domain_create(struct domain *d, unsigned int
> domcr_flags,
> /* PV/PVH guests get an emulated PIT too for video BIOSes to use. */
> pit_init(d, cpu_khz);
>
> +/*
> + * If the FPU not to save FCS/FDS then we
On 23/02/16 11:05, David Vrabel wrote:
> The hardware may not write the FIP/FDP fields with a XSAVE*
> instruction. e.g., with XSAVEOPT/XSAVES if the state hasn't changed
> or on AMD CPUs when a floating point exception is not pending. We
> need to identify this case so we can correctly apply the
On 23/02/16 11:05, David Vrabel wrote:
> The HVM parameter HVM_PARAM_X87_FIP_WIDTH to allow tools and the guest
> to adjust the width of the FIP/FDP registers to be saved/restored by
> the hypervisor. This is in case the hypervisor hueristics do not do
> the right thing.
>
> Add this parameter to
Hi all,
I am planning to make some modifications to the OpenStack docs in the next few
days. The bug outlining the changes are at
https://bugs.launchpad.net/openstack-manuals/+bug/1548403 - if you know of any
additional known issues, please comment on this thread or comment directly on
the bug
On 2016/2/9 13:04, Rob Herring wrote:
> On Thu, Feb 4, 2016 at 9:05 PM, Shannon Zhao wrote:
>> From: Shannon Zhao
>>
>> Sometimes it needs to check if there is a node in FDT by full path.
>
> I'm confused. Are you searching by full path or...
>
>> Introduce this helper to get the specified na
Patches 1 and 2 are meant to go in. Patch 3 is a prerequisite to patch
4 and may go in as well, but patch 4 is RFC because with the Pericom
board I have MSI doesn't appear to function. Since it also does not
work in baremetal Linux when doing the trivial adjustments needed in
its driver, I suspect
Signed-off-by: Olaf Hering
Acked-by: Ian Campbell
Acked-by: Wei Liu
Cc: Ian Campbell
Cc: Ian Jackson
Cc: Jan Beulich
Cc: Keir Fraser
Cc: Tim Deegan
---
xen/include/public/io/vscsiif.h | 69 +
1 file changed, 69 insertions(+)
diff --git a/xen/include
The pvops kernel expects either "naa.WWN:LUN" or "h:c:t:l" in the p-dev
property. Add the missing :LUN part to the comment.
Signed-off-by: Olaf Hering
Acked-by: Ian Campbell
Acked-by: Wei Liu
Cc: Ian Campbell
Cc: Ian Jackson
Cc: Jan Beulich
Cc: Keir Fraser
Cc: Tim Deegan
---
xen/include/p
Signed-off-by: Olaf Hering
Cc: Ian Jackson
Cc: Stefano Stabellini
Cc: Ian Campbell
Cc: Wei Liu
---
tools/libxl/libxl.c | 2 +-
tools/libxl/libxl_internal.h | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/tools/libxl/libxl.c b/tools/libxl/libxl.c
index 2bde0f5..0b
Port vscsi=[] and scsi-{attach,detach,list} commands from xend to libxl.
libvirt uses its existing SCSI support:
http://lists.xenproject.org/archives/html/xen-devel/2015-04/msg02963.html
targetcli/rtslib has to be aware of xen-scsiback (upstream unresponsive):
http://article.gmane.org/gmane.linux
Subsequent changes will want to use this pointer.
This makes the enable_ro structure member redundant, so it gets dropped
at once.
Signed-off-by: Jan Beulich
--- a/xen/drivers/char/ns16550.c
+++ b/xen/drivers/char/ns16550.c
@@ -74,7 +74,7 @@ static struct ns16550 {
u32 bar64;
u16 cr;
Just to make them public, not meant for merging:
The scripts used during development to create a bunch of SCSI devices in
dom0 using the Linux target framework. targetcli3 and rtslib3 is used.
A patch is required for python-rtslib:
http://article.gmane.org/gmane.linux.scsi.target.devel/8146
Signe
Port pvscsi support from xend to libxl:
vscsi=['pdev,vdev{,options}']
xl scsi-attach
xl scsi-detach
xl scsi-list
Signed-off-by: Olaf Hering
Cc: Ian Jackson
Cc: Stefano Stabellini
Cc: Ian Campbell
Cc: Wei Liu
---
docs/man/xl.cfg.pod.5| 56 ++
docs/man/xl.pod.1
Signed-off-by: Olaf Hering
Acked-by: Ian Campbell
Acked-by: Wei Liu
Cc: Ian Campbell
Cc: Ian Jackson
Cc: Jan Beulich
Cc: Keir Fraser
Cc: Tim Deegan
---
docs/misc/xenstore-paths.markdown | 10 ++
1 file changed, 10 insertions(+)
diff --git a/docs/misc/xenstore-paths.markdown
b/doc
Other than the controllers supported so far, multiple port Pericom
boards map all of their ports via BAR0, which requires a number of
adjustments: Instead of tracking "max_bars" we now flag whether all
ports use BAR0, and whether to expect a port-I/O or MMIO resource. As
a result pci_uart_config()
In order for a Xen internal PCI device driver to enable MSI on the
device, we need another hook which the driver can use to create the IRQ
(doing this in the init_preirq hook is too early, since IRQ code hasn't
got initialized at that time yet, and doing it in init_postirq is too
late because at le
Which, on x86, requires fiddling with the INTx bit in PCI config space,
since for internally used MSI we can't delegate this to Dom0.
ns16550_init_postirq() also needs (benign) re-ordering of its
operations.
Signed-off-by: Jan Beulich
---
RFC reason: No interrupts occur for an unknown reason (pr
> On February 11, 2016 1:01am, Jan Beulich wrote:
> >>> On 05.02.16 at 11:18, wrote:
> > This patch checks all kinds of error and all the way up the call trees
> > of VT-d Device-TLB flush(IOMMU part).
> > @@ -171,7 +172,10 @@ void __hwdom_init iommu_hwdom_init(struct
> domain *d)
> >
On Fri, Feb 19, 2016 at 9:51 AM, Huaitong Han wrote:
> 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[
On 23/02/16 11:10, Andrew Cooper wrote:
> On 23/02/16 11:05, David Vrabel wrote:
>> @@ -653,6 +657,12 @@ int arch_domain_create(struct domain *d, unsigned int
>> domcr_flags,
>> /* PV/PVH guests get an emulated PIT too for video BIOSes to use. */
>> pit_init(d, cpu_khz);
>>
>> +/*
On 23/02/16 11:18, Andrew Cooper wrote:
> On 23/02/16 11:05, David Vrabel wrote:
>> The hardware may not write the FIP/FDP fields with a XSAVE*
>> instruction. e.g., with XSAVEOPT/XSAVES if the state hasn't changed
>> or on AMD CPUs when a floating point exception is not pending. We
>> need to id
On 23/02/16 07:24, Luis R. Rodriguez wrote:
> --- a/arch/x86/xen/enlighten.c
> +++ b/arch/x86/xen/enlighten.c
[...]
> @@ -1526,8 +1525,6 @@ asmlinkage __visible void __init xen_start_kernel(void)
>
> /* Install Xen paravirt ops */
> pv_info = xen_info;
> - if (xen_initial_domain()
On 02/23/2016 08:09 AM, Jan Beulich wrote:
On 22.02.16 at 22:14, wrote:
>
> (Please trim you replies.)
>
>> Ping: Or would you prefer resubmitting with the comments so far?
>
> Either way is fine. It's on my list of thing to look at, but being RFC
> it ranges priority wise behind various
On 2016/1/27 23:41, Stefano Stabellini wrote:
> On Sat, 23 Jan 2016, Shannon Zhao wrote:
>> From: Shannon Zhao
>>
>> There are two flags: PSCI_COMPLIANT and PSCI_USE_HVC. When set, the
>> former signals to the OS that the hardware is PSCI compliant. The latter
>> selects the appropriate conduit
Hi Akanksha,
Jesus is teaching today.
But having chatted to some people on #metrics-grimoire the first step is to set
up an environment and play with it. To do so, you will need
kibana and elasticsearch - packages for these should be in any distro and can
be installed via apt-get or yum
The t
On 08/02/16 13:19, Dario Faggioli wrote:
> In fact, they look rather useless: they are never
> referenced neither directly, nor via the sched_data
> pointer, as a dynamic copy that overrides them is
> allocated as the very first step of a scheduler's
> initialization.
>
> While there, take the cha
This macro doesn't really provide a benefit. When support is added the
implementer can implement this how it needs to be and not conform to the
macro. Additionally this change limits the output of the warning to just
once instead of nrpages worth. While editing this area I dropped
trailing whitespa
flight 83624 qemu-upstream-4.6-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/83624/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stopfail REGR. vs. 82482
test-amd64-i386-
On 23/02/16 13:12, Doug Goldstein wrote:
> This macro doesn't really provide a benefit. When support is added the
> implementer can implement this how it needs to be and not conform to the
> macro. Additionally this change limits the output of the warning to just
> once instead of nrpages worth. Wh
On 23/02/16 13:42, Andrew Cooper wrote:
> On 23/02/16 13:12, Doug Goldstein wrote:
>> This macro doesn't really provide a benefit. When support is added the
>> implementer can implement this how it needs to be and not conform to the
>> macro. Additionally this change limits the output of the warnin
On 02/22/2016 09:04 PM, Haozhong Zhang wrote:
+if ( cpu_has_tsc_ratio )
+svm_function_table.tsc_scaling.ratio_frac_bits = 32;
+
+#define hvm_tsc_scaling_supported \
+(!!hvm_funcs.tsc_scaling.ratio_frac_bits)
+
What is the difference (in usage) between cpu_has_tsc_rati
>>> On 23.02.16 at 12:54, wrote:
> On 23/02/16 11:18, Andrew Cooper wrote:
>> On 23/02/16 11:05, David Vrabel wrote:
>>> The hardware may not write the FIP/FDP fields with a XSAVE*
>>> instruction. e.g., with XSAVEOPT/XSAVES if the state hasn't changed
>>> or on AMD CPUs when a floating point exc
>>> On 23.02.16 at 15:00, wrote:
> On 02/22/2016 09:04 PM, Haozhong Zhang wrote:
>
>>
>> +if ( cpu_has_tsc_ratio )
>> +svm_function_table.tsc_scaling.ratio_frac_bits = 32;
>> +
>
>
>>
>> +#define hvm_tsc_scaling_supported \
>> +(!!hvm_funcs.tsc_scaling.ratio_frac_bits)
>>
On Tue, 23 Feb 2016, five wrote:
> setenv xen_bootargs 'sync_console console=dtuart dtuart=serial2'
> setenv dom0_bootargs 'console=hvc0,115200n8 earlyprintk=xen debug
> ignore_loglevel root=/dev/mmcblk0p2 rw
[...]
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to
>
On 02/23/2016 09:10 AM, Jan Beulich wrote:
On 23.02.16 at 15:00, wrote:
On 02/22/2016 09:04 PM, Haozhong Zhang wrote:
+if ( cpu_has_tsc_ratio )
+svm_function_table.tsc_scaling.ratio_frac_bits = 32;
+
+#define hvm_tsc_scaling_supported \
+(!!hvm_funcs.tsc_scaling.rat
Hi Ian
On 23 February 2016 at 18:00, Ian Campbell wrote:
> On Mon, 2016-02-22 at 17:29 +0800, Fu Wei wrote:
>> Hi Julien,
>>
>> On 20 February 2016 at 00:28, Julien Grall
>> wrote:
>> > Xen is currently crashing because of malformed compatible property for
>> > the boot module. This is because t
>
> >
> > Great, that settles arch_hvm_event_fill_regs -> vm_event_fill_regs.
> > Should I then do the same for arch_monitor_get_capabilities (->
> > vm_event_monitor_get_capabilities)?
>
> Sounds good to me, so yes, unless Tamas or Jan think otherwise.
>
SGTM too.
Tamas
_
On Mon, Feb 22, 2016 at 04:28:19AM -0700, Jan Beulich wrote:
> >>> On 19.02.16 at 17:05, wrote:
> > On Wed, Feb 17, 2016 at 05:28:08PM +, Wei Liu wrote:
> >> Hi all
> >>
> >> Tools people are in the process of splitting libxenctrl into a set of
> >> stable libraries. One of the proposed libra
>
> 2) For Tamas: would it be ok if I put p2m_get_vcpu_altp2m_idx in
> asm/altp2m.h and rename it to altp2m_vcpu_idx(v) (to obey function-naming
> pattern in that file)?
>
Yes, that works.
Tamas
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://
On Tue, 23 Feb 2016, Shannon Zhao wrote:
> On 2016/1/27 23:41, Stefano Stabellini wrote:
> > On Sat, 23 Jan 2016, Shannon Zhao wrote:
> >> From: Shannon Zhao
> >>
> >> There are two flags: PSCI_COMPLIANT and PSCI_USE_HVC. When set, the
> >> former signals to the OS that the hardware is PSCI compli
On 2/23/2016 4:30 PM, Tamas K Lengyel wrote:
2) For Tamas: would it be ok if I put p2m_get_vcpu_altp2m_idx in
asm/altp2m.h and rename it to altp2m_vcpu_idx(v) (to obey
function-naming pattern in that file)?
Yes, that works.
Tamas
Thanks. Any thoughts on 3)?
Corneliu.
>>> On 23.02.16 at 12:05, wrote:
> --- a/xen/arch/x86/xstate.c
> +++ b/xen/arch/x86/xstate.c
> @@ -263,41 +263,24 @@ void xsave(struct vcpu *v, uint64_t mask)
>
> if ( word_size <= 0 || !is_pv_32bit_vcpu(v) )
> {
> -typeof(ptr->fpu_sse.fip.sel) fcs = ptr->fpu_sse.fip.sel;
> -
>>> On 23.02.16 at 12:05, wrote:
> @@ -292,17 +296,17 @@ void xsave(struct vcpu *v, uint64_t mask)
> asm volatile ( "fnstenv %0" : "=m" (fpu_env) );
> ptr->fpu_sse.fip.sel = fpu_env.fcs;
> ptr->fpu_sse.fdp.sel = fpu_env.fds;
> -word_size = 4;
> +
>>> On 23.02.16 at 15:16, wrote:
> On 02/23/2016 09:10 AM, Jan Beulich wrote:
> On 23.02.16 at 15:00, wrote:
>>> On 02/22/2016 09:04 PM, Haozhong Zhang wrote:
>>>
+if ( cpu_has_tsc_ratio )
+svm_function_table.tsc_scaling.ratio_frac_bits = 32;
+
>>>
On 2/23/16 7:45 AM, Andrew Cooper wrote:
> On 23/02/16 13:42, Andrew Cooper wrote:
>> On 23/02/16 13:12, Doug Goldstein wrote:
>>> This macro doesn't really provide a benefit. When support is added the
>>> implementer can implement this how it needs to be and not conform to the
>>> macro. Additiona
>>> On 23.02.16 at 15:31, wrote:
> On Mon, Feb 22, 2016 at 04:28:19AM -0700, Jan Beulich wrote:
>> >>> On 19.02.16 at 17:05, wrote:
>> > On Wed, Feb 17, 2016 at 05:28:08PM +, Wei Liu wrote:
>> >> Hi all
>> >>
>> >> Tools people are in the process of splitting libxenctrl into a set of
>> >> s
>>> On 23.02.16 at 12:43, wrote:
>> On February 11, 2016 1:01am, Jan Beulich wrote:
>> >>> On 05.02.16 at 11:18, wrote:
>> > This patch checks all kinds of error and all the way up the call trees
>> > of VT-d Device-TLB flush(IOMMU part).
>> > @@ -171,7 +172,10 @@ void __hwdom_init iommu_hwdom_
>>> On 23.02.16 at 16:38, wrote:
> On 2/23/16 7:45 AM, Andrew Cooper wrote:
>> On 23/02/16 13:42, Andrew Cooper wrote:
>>> On 23/02/16 13:12, Doug Goldstein wrote:
This macro doesn't really provide a benefit. When support is added the
implementer can implement this how it needs to be and
>>> On 10.02.16 at 11:09, wrote:
> % Xen PV IOMMU interface
> % Malcolm Crossley <>
> Paul Durrant <>
> % Draft D
>
> Introduction
>
>
> Revision History
>
>
>
> Version Date Changes
>
On 23/02/16 16:17, Jan Beulich wrote:
On 10.02.16 at 11:09, wrote:
>> % Xen PV IOMMU interface
>> % Malcolm Crossley <>
>> Paul Durrant <>
>> % Draft D
>>
>> Introduction
>>
>>
>> Revision History
>>
>>
>> ---
On 23/02/16 15:24, Jan Beulich wrote:
On 23.02.16 at 12:05, wrote:
>> @@ -292,17 +296,17 @@ void xsave(struct vcpu *v, uint64_t mask)
>> asm volatile ( "fnstenv %0" : "=m" (fpu_env) );
>> ptr->fpu_sse.fip.sel = fpu_env.fcs;
>> ptr->fpu_sse.fdp.sel = fpu_
The use of MAP_SMALL_PAGES causes shattering of the superpages making up the
Xen virtual region, and is counter to the purpose of this series.
Furthermore, it is not required for the memguard infrastructure to function
(which itself uses map_pages_to_xen() for creating holes).
Signed-off-by: Andre
And make use of NX and RO attributes wherever possible.
After this series, the pagetable layout looks like:
(XEN) *** Dumping Xen text/data/bss mappings from 82d08000
(XEN) cr3 000826484000, idle_pg_table 82d080818000, pa ac018000
(XEN) l2_xenmap: 82d080814000, pa
In preparation for using superpage mappings, .data and .bss will both want to
be mapped as read-write. By making them adjacent, they can share the same
superpage and will not require superpage alignment between themselves.
While making this change, fix an exposed alignment bug. __init_end only n
Because of the new 2M alignment of .init and .bss, the existing memory
guarding infrastructure causes a shattered 2M superpage with non-present
entries for .init, and present entries for the alignment space.
Do away with the difference in behaviour between debug and non-debug builds;
always destro
The entire contents of .lockprofile.data are unchanging pointers to
lock_profile structure in .data. Annotate the type as such, and link the
section in .rodata. As these are just pointers, there is no need for 32byte
alignment.
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
CC: Ian Campbell
>>> On 23.02.16 at 09:34, wrote:
> +static void vmx_vcpu_block(struct vcpu *v)
> +{
> +unsigned long flags;
> +unsigned int dest;
> +spinlock_t *old_lock = pi_blocking_list_lock(v);
> +spinlock_t *pi_blocking_list_lock =
> &vmx_pi_blocking_list_lock(v->processor);
> +struct pi
1 - 100 of 161 matches
Mail list logo
