On Mon, 2015-10-12 at 09:38 +0100, Ian Campbell wrote:
> The next Xen technical call will be at:
> Wed 14 Oct 17:00:00 BST 2015
> `date -d @1444838400`
No agenda => no call.
___
Xen-devel mailing list
Xen-devel@lists.xen.org
On Wed, 7 Oct 2015, Ian Campbell wrote:
> In Xen 4.7 we are refactoring parts libxenctrl into a number of
> separate libraries which will provide backward and forward API and ABI
> compatiblity.
>
> Specifically libxenevtchn, libxengnttab and libxenforeignmemory.
>
> Previous patches have
schedule_cpu_switch() is meant to be only used for moving
pCPUs from a cpupool to no cpupool, and from there back
to a cpupool, *not* to move them directly from one cpupool
to another.
This is something that is reflected in the way it is
implemented, and should be kept in mind when looking at
it.
Idle vCPUs are set to run immediately, as a part of their
own initialization, so we shouldn't even try to put them
in a runqueue. In fact, actual schedulers don't do that,
even when asked to (that is rather explicit in Credit2
and RTDS, a bit less evident in Credit1).
Let's make things look as
As, curently, there is no reason for bothering having
it and keeping it updated.
In fact, it is only used for dumping and changing
vCPUs parameters, but that can be achieved easily with
for_each_vcpu.
While there, improve alignment of comments, ad
add a const qualifier to a pointer, making
flight 62954 linux-mingo-tip-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/62954/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-pvh-intel 6 xen-boot fail REGR. vs. 60684
As, curently, there is no reason for bothering having
it and keeping it updated.
In fact, it is only used for dumping and changing
vCPUs parameters, but that can be achieved easily with
for_each_vcpu.
While there, take care of the case when
XEN_DOMCTL_SCHEDOP_getinfo is called but no vCPUs have
>>> On 02.10.15 at 17:48, wrote:
> --- a/xen/arch/x86/hvm/irq.c
> +++ b/xen/arch/x86/hvm/irq.c
> @@ -330,6 +330,10 @@ void hvm_set_callback_via(struct domain *d, uint64_t
> via)
> (via_type > HVMIRQ_callback_vector) )
> via_type = HVMIRQ_callback_none;
>
On Wed, 7 Oct 2015, Ian Campbell wrote:
> Using an existing libxenctrl handle after a fork was never
> particularly safe (especially if foreign mappings existed at the time
> of the fork) and the xc fd has been unavailable for many releases.
>
> Reopen the handle after fork and therefore do away
On Wed, 2015-10-14 at 15:11 +0100, Stefano Stabellini wrote:
> On Wed, 14 Oct 2015, Ian Campbell wrote:
> > On Wed, 2015-10-14 at 14:51 +0100, Stefano Stabellini wrote:
> > > I am very practical in this regard and I just don't want the raisin
> > > build to fail on arm64 with xen 4.6. We could
On Wed, 2015-10-14 at 14:08 +0100, Wei Liu wrote:
> On Wed, Oct 14, 2015 at 01:21:11PM +0100, Ian Campbell wrote:
> > Aside: I'm a bit confused regarding whether our "stable release scheme" is
> > defined in terms of number of concurrently supported releases or in terms
> > of an absolute time.
>
On Wed, 2015-10-14 at 16:41 +0100, Stefano Stabellini wrote:
> On Wed, 14 Oct 2015, Ian Campbell wrote:
> > On Wed, 2015-10-14 at 15:10 +0100, Stefano Stabellini wrote:
> > > On Wed, 7 Oct 2015, Ian Campbell wrote:
> > > > In Xen 4.7 we are refactoring parts libxenctrl into a number of
> > > >
On 14/10/15 14:31, Jan Beulich wrote:
> --- a/xen/include/asm-x86/cpufeature.h
> +++ b/xen/include/asm-x86/cpufeature.h
> @@ -170,6 +170,7 @@
> #define CPUID5_ECX_EXTENSIONS_SUPPORTED 0x1
> #define CPUID5_ECX_INTERRUPT_BREAK 0x2
>
> +#define cpu_has_fpu
>>> On 14.10.15 at 16:30, wrote:
> On 14/10/15 14:31, Jan Beulich wrote:
>> --- a/xen/include/asm-x86/cpufeature.h
>> +++ b/xen/include/asm-x86/cpufeature.h
>> @@ -170,6 +170,7 @@
>> #define CPUID5_ECX_EXTENSIONS_SUPPORTED 0x1
>> #define CPUID5_ECX_INTERRUPT_BREAK
On Wed, 2015-10-07 at 16:08 +0100, George Dunlap wrote:
> On 07/10/15 15:15, Ian Campbell wrote:
> >
[...]
> > Signed-off-by: Ian Campbell
> > Acked-by: George Dunlap
> > Cc: George Dunlap
> >
[...]
> In any case:
On Wed, 2015-10-14 at 15:01 +0100, Stefano Stabellini wrote:
> On Wed, 7 Oct 2015, Ian Campbell wrote:
> > In Xen 4.7 we are refactoring parts libxenctrl into a number of
> > separate libraries which will provide backward and forward API and ABI
> > compatiblity.
> >
> > One such library will be
>>> On 02.10.15 at 17:48, wrote:
> Signed-off-by: Roger Pau Monné
> Cc: Jan Beulich
> Cc: Andrew Cooper
> ---
> Changes since v6:
> - Return ENODEV in pmtimer_load if the timer is disabled.
> -
>> >>> On 13.10.2015 at 22:50 wrote:
> >>> On 13.10.15 at 16:29, wrote:
> >> > >>>On 29.09.2015 at 15:22 wrote:
> >> >>> On 29.09.15 at 04:53, wrote:
> >> Monday, September 28, 2015 2:47 PM,
El 14/10/15 a les 16.59, Boris Ostrovsky ha escrit:
> On 10/14/2015 10:41 AM, Jan Beulich wrote:
> On 02.10.15 at 17:48, wrote:
>>> Instead of choosing the interface to expose to guests based on the guest
>>> type, do it based on whether the guest has an emulated local
Hey,
Here it comes v2 of this series. It took a bit more than how I wanted, mostly
because of the cpufreq issue I found while testing (as I though I was causing
it! :-/).
Version 1 is here:
http://www.gossamer-threads.com/lists/xen/devel/401619?page=last
I think I've addressed all the review
In fact, csched_vcpu_remove() (i.e., the credit1
implementation of remove_vcpu()) manipulates runqueues,
so holding the runqueue lock is necessary.
Also, while there, *_lock_irq() (for the private lock) is
enough, there is no need to *_lock_irqsave().
Signed-off-by: Dario Faggioli
On 14/10/15 16:54, Jan Beulich wrote:
On 02.10.15 at 17:48, wrote:
>> --- a/xen/arch/x86/hvm/irq.c
>> +++ b/xen/arch/x86/hvm/irq.c
>> @@ -330,6 +330,10 @@ void hvm_set_callback_via(struct domain *d, uint64_t
>> via)
>> (via_type > HVMIRQ_callback_vector) )
>>
On Wed, 2015-10-14 at 16:59 +0100, Ian Campbell wrote:
> I came up with the following patch[...]
> if (!xendev->dev) {
> +if (con->string) {
I've fixed the obvious typo in my actual tree...
> +munmap(con->sring, XC_PAGE_SIZE);
> +con->sring = NULL;
> +
>>> On 02.10.15 at 17:48, wrote:
> Signed-off-by: Roger Pau Monné
Acked-by: Jan Beulich
(but awaiting an update to patch 2 for it to go in)
___
Xen-devel mailing list
>>> On 02.10.15 at 17:48, wrote:
> Instead of choosing the interface to expose to guests based on the guest
> type, do it based on whether the guest has an emulated local apic or not.
>
> Signed-off-by: Roger Pau Monné
Acked-by: Jan Beulich
On Wed, 7 Oct 2015, Ian Campbell wrote:
> Until the previous patch this relied on xc_fd(), which was only
> implemented for Xen 4.0 and earlier.
>
> I stopped short of disabling this by default, although I think there's
> a pretty strong argument for doing so.
>
> Removing this support drops the
On 14/10/15 14:31, Jan Beulich wrote:
> Their initialization happens without races, so there's no point in
> using atomic (locked) operations to update the respective flags.
> (There's one case where the clear_bit() was completely pointless.)
>
> Also drop a neighboring stale comment from AMD
>> >>>On 13.10.2015 at 17:35, wrote:
> At 11:09 + on 11 Oct (1444561760), Xu, Quan wrote:
> What in particular is
On 14/10/15 16:05, Ian Campbell wrote:
> On Wed, 2015-10-07 at 16:08 +0100, George Dunlap wrote:
>> On 07/10/15 15:15, Ian Campbell wrote:
>>>
> [...]
>>> Signed-off-by: Ian Campbell
>>> Acked-by: George Dunlap
>>> Cc: George Dunlap
On Wed, 14 Oct 2015, Ian Campbell wrote:
> On Wed, 2015-10-14 at 15:01 +0100, Stefano Stabellini wrote:
> > On Wed, 7 Oct 2015, Ian Campbell wrote:
> > > In Xen 4.7 we are refactoring parts libxenctrl into a number of
> > > separate libraries which will provide backward and forward API and ABI
> >
On 10/14/2015 10:41 AM, Jan Beulich wrote:
On 02.10.15 at 17:48, wrote:
Instead of choosing the interface to expose to guests based on the guest
type, do it based on whether the guest has an emulated local apic or not.
Signed-off-by: Roger Pau Monné
On 10/14/2015 11:06 AM, Roger Pau Monné wrote:
El 14/10/15 a les 16.59, Boris Ostrovsky ha escrit:
On 10/14/2015 10:41 AM, Jan Beulich wrote:
On 02.10.15 at 17:48, wrote:
Instead of choosing the interface to expose to guests based on the guest
type, do it based on
The insert_vcpu() hook is handled with inconsistent locking.
In fact, schedule_cpu_switch() calls the hook with runqueue
lock held, while sched_move_domain() relies on the hook
implementations to take the lock themselves (and, since that
is not done in Credit1 and RTDS, such operation is not safe
Signed-off-by: Stefano Stabellini
---
lib/common-functions.sh |7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/lib/common-functions.sh b/lib/common-functions.sh
index 03642ae..27f6434 100644
--- a/lib/common-functions.sh
+++
Disable ovmf build on x86_32: it does not work, the code was already
forcing a x86_64 build.
---
Changes in v2:
- disable x86_32 build (it doesn't work, but it wasn't explicitly
disabled)
- remove export GCC48_AARCH64_PREFIX= as it is not necessary
- add a comment on why we are using -t GCC48
On Wed, 2015-10-14 at 16:57 +0100, Stefano Stabellini wrote:
> Disable ovmf build on x86_32: it does not work, the code was already
> forcing a x86_64 build.
FYI osstest builds OVMF (64-bit) in its build-i386 jobs just fine. e.g. in
[0]. That's useful in 32-on-64 type scenarios, maybe raisin
Hi all,
this small patch series enable cpu_hotplug in ARM and ARM64 guests,
using the PV path to plug and unplug the cpus and psci to enable/disable
them.
Stefano Stabellini (3):
xen/arm: Enable cpu_hotplug.c
xen, cpu_hotplug: call device_offline instead of cpu_down
xen/arm:
Build cpu_hotplug for ARM and ARM64 guests.
Rename arch_(un)register_cpu to xen_(un)register_cpu and provide an
empty implementation on ARM and ARM64. On x86 just call
arch_(un)register_cpu as we are already doing.
Initialize cpu_hotplug on ARM.
Signed-off-by: Stefano Stabellini
When offlining a cpu, instead of cpu_down, call device_offline, which
also takes care of updating the cpu.dev.offline field. This keeps the
sysfs file /sys/devices/system/cpu/cpuN/online, up to date. Also move
the call to disable_hotplug_cpu, because it makes more sense to have it
there.
CentOS 7 now aliases acpica-tools instead of iasl, making its deps
essentially the same as Fedora. Add iasl|acpica-tools as an alias in
the Fedora deps, and make the CentOS deps a straight clone of the
Fedora deps (as they are for the other components).
Signed-off-by: George Dunlap
Add systemd development libraries if we detect systemd present on the system
Signed-off-by: George Dunlap
---
components/xen | 10 ++
1 file changed, 10 insertions(+)
diff --git a/components/xen b/components/xen
index 090cceb..93ed288 100644
---
At the moment, something like 7.1.1503 will be parsed as RELEASE=7.1
UPDATE=1503. Change the bash string so that RELEASE=7 UPDATE=1.1503
in this case.
Also add an example CentOS 7 release string, and add the RELEASE /
UPDATE parsing to lsb_release as well.
Signed-off-by: George Dunlap
It's not uncommon for packages to be renamed, and for package managers
to know the translation from old packages to new packages. For
example:
# apt-get install pciutils-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'libpci-dev'
Signed-off-by: Stefano Stabellini
---
arch/arm/xen/enlighten.c |6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/xen/enlighten.c b/arch/arm/xen/enlighten.c
index 6c09cc4..59f5421 100644
--- a/arch/arm/xen/enlighten.c
+++
On October 14, 2015 1:49:55 PM EDT, Stefano Stabellini
wrote:
>Build cpu_hotplug for ARM and ARM64 guests.
>
>Rename arch_(un)register_cpu to xen_(un)register_cpu and provide an
>empty implementation on ARM and ARM64. On x86 just call
>arch_(un)register_cpu as
Miscellaneous improvements
George Dunlap (5):
raisin: Handle aliases for packages, add pciutils-dev / libpci-dev
alias
raisin: Detect systemd
raisin: Allow iasl to alias acpica-tools, unify Fedora and CentOS deps
for xen
raisin: Change update/release parsing OSes
raisin: Add
Allowing the user to enable or disable specific functionality, such as
stubdoms.
Signed-off-by: George Dunlap
---
components/xen| 2 +-
configs/config-4.5| 4
configs/config-4.6| 4
configs/config-master | 4
4 files changed, 13
On 14/10/15 17:21, George Dunlap wrote:
> Add systemd development libraries if we detect systemd present on the system
>
> Signed-off-by: George Dunlap
Sorry, meant to add a comment here...
> ---
> components/xen | 10 ++
> 1 file changed, 10 insertions(+)
>
On 14/10/15 17:24, Roger Pau Monne wrote:
> Introduce a new filed to signal if the FPU has been initialised or not. Xen
"field", I am guessing?
> diff --git a/xen/include/public/arch-x86/hvm/save.h
> b/xen/include/public/arch-x86/hvm/save.h
> index c7560f2..c4863be 100644
> ---
On Wed, 14 Oct 2015, Ian Campbell wrote:
> On Wed, 2015-10-14 at 17:29 +0100, Stefano Stabellini wrote:
>
> > > Obviously the call to xen_be_unbind_evtchn is not useful as is, but I do
> > > wonder where the evtchn which the primary console must have somewhere
> > > actually is then...
> >
> >
On Wed, Oct 14, 2015 at 06:24:40PM +0200, Roger Pau Monne wrote:
> This reverts commit d64dbbcc7c9934a46126c59d78536235908377ad.
>
> Xen always set the FPU as initialized when loading a HVM context, so libxc
> has to provide a valid FPU context when setting the CPU registers.
>
> This is a
This reverts commit d64dbbcc7c9934a46126c59d78536235908377ad.
Xen always set the FPU as initialized when loading a HVM context, so libxc
has to provide a valid FPU context when setting the CPU registers.
This is a stop-gap measure in order to unblock OSSTest Windows 7 failures
while a proper fix
On Wed, 2015-10-14 at 17:29 +0100, Stefano Stabellini wrote:
> > Obviously the call to xen_be_unbind_evtchn is not useful as is, but I do
> > wonder where the evtchn which the primary console must have somewhere
> > actually is then...
>
> Actually I think that xen_be_unbind_evtchn might be
Introduce a new filed to signal if the FPU has been initialised or not. Xen
needs this new filed in order to know whether to set the FPU as initialised
or not during restore of CPU context. Previously Xen always wrongly assumed
the FPU was initialised on restore.
Signed-off-by: Roger Pau Monné
In order to cope with types having multiple compat versions pass a parameter
to the fixup function so we can identify which compat version Xen is dealing
with.
Signed-off-by: Roger Pau Monné
Cc: Ian Campbell
Cc: Ian Jackson
Hello,
This patch series tries to properly solve the problem seen with the HVMlite
series, that Xen always assumes the FPU is initialised on CPU context
restore.
Since I don't have a pre-3.4 Xen box, I would like to request if this patch
series can be tested by the XenServer CI loop, which
On Wed, 14 Oct 2015, Ian Campbell wrote:
> On Wed, 2015-10-14 at 16:41 +0100, Stefano Stabellini wrote:
> > On Wed, 14 Oct 2015, Ian Campbell wrote:
> > > On Wed, 2015-10-14 at 15:10 +0100, Stefano Stabellini wrote:
> > > > On Wed, 7 Oct 2015, Ian Campbell wrote:
> > > > > In Xen 4.7 we are
Hi everyone,
I wanted to walk you through some of the results of the Review Process study
https://github.com/dicortazar/ipython-notebooks/blob/master/projects/xen-analysis/Code-Review-Metrics.ipynb
I am also looking for input and views.
Best Regards
Lars
== Caveats ==
C1) Only 60% percent
On Tue, 2015-10-13 at 16:53 +0800, He Chen wrote:
> diff --git a/docs/misc/xl-psr.markdown b/docs/misc/xl-psr.markdown
> index c32e25c..9b08ee3 100644
> --- a/docs/misc/xl-psr.markdown
> +++ b/docs/misc/xl-psr.markdown
> @@ -127,6 +127,59 @@ Per domain CBM settings can be shown by:
>
> `xl
Hi Ian,
When I now try to use standalone script for debug, it seems doesn't work as
before. Any usage changed?
[root@robert-ivt osstest]# ./standalone run-job --dry-run -h dummy
test-amd64-amd64-qemuu-nested
Could not open a connection to your authentication agent.
WARNING: Unable to access
>>> On 14.10.15 at 07:12, wrote:
> Jan Beulich wrote on 2015-10-13:
> On 13.10.15 at 07:27, wrote:
>>> Jan Beulich wrote on 2015-10-12:
>>> On 12.10.15 at 03:42, wrote:
> So, my suggestion is that we can rely on
The variable new_data is initialized to NULL and free but never
allocated neither used.
Signed-off-by: Julien Grall
---
xen/arch/arm/domain_build.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/xen/arch/arm/domain_build.c b/xen/arch/arm/domain_build.c
index
> -Original Message-
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Wednesday, October 14, 2015 5:46 PM
> To: Wu, Feng
> Cc: Andrew Cooper ; xen-devel@lists.xen.org;
> Keir Fraser
> Subject: RE: [PATCH v8 02/17] Add
On Wed, 2015-10-14 at 10:38 +0800, Chao Peng wrote:
> > diff --git a/tools/libxl/xl_cmdimpl.c b/tools/libxl/xl_cmdimpl.c
> > index 365798b..8db0132 100644
> > --- a/tools/libxl/xl_cmdimpl.c
> > +++ b/tools/libxl/xl_cmdimpl.c
> > @@ -8434,6 +8434,8 @@ static int psr_cat_hwinfo(void)
> > }
Hi Jan,
After some thinking, just set/clear p2m->ept.ept_ad is not enough -- we
also need to __vmwrite it to VMCS's EPTP, and then call ept_sync_domain.
I have verified attached patch can work.
Which implementation would you prefer, existing code or with attached
patch? If you prefer the
On Wed, 2015-10-14 at 11:08 +0200, Dario Faggioli wrote:
> On Tue, 2015-10-13 at 16:53 +0800, He Chen wrote:
> > diff --git a/docs/misc/xl-psr.markdown b/docs/misc/xl-psr.markdown
> > index c32e25c..9b08ee3 100644
> > --- a/docs/misc/xl-psr.markdown
> > +++ b/docs/misc/xl-psr.markdown
> > @@
> -Original Message-
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Wednesday, October 14, 2015 5:06 PM
> To: Wu, Feng
> Cc: Andrew Cooper ; xen-devel@lists.xen.org;
> Keir Fraser
> Subject: RE: [PATCH v8 02/17] Add
> -Original Message-
> From: Ian Campbell [mailto:ian.campb...@citrix.com]
> Sent: Wednesday, October 14, 2015 5:48 PM
> To: Hu, Robert ; ian.jack...@citrix.com
> Cc: xen-devel@lists.xen.org
> Subject: Re: OSSTest standalone script
>
> On Wed, 2015-10-14 at 09:29
>>> On 14.10.15 at 07:57, wrote:
>
>> -Original Message-
>> From: Jan Beulich [mailto:jbeul...@suse.com]
>> Sent: Tuesday, October 13, 2015 11:29 PM
>> To: Wu, Feng
>> Cc: Andrew Cooper ; xen-devel@lists.xen.org;
>> Keir
On 13/10/15 22:14, Daniel Kiper wrote:
> On Tue, Oct 13, 2015 at 11:55:09AM +0100, Ian Campbell wrote:
>> [CCing Daniel]
>>
>> Daniel, please could you advice on which Xen releases, guest types and
>> guest kernel versions are currently expected to work with memory hotplug.
>
> Well... It worked,
This is exactly what we're looking to do. Do you know of any relevant areas
in the Xen source code where this may be taking place?
On Mon, Oct 5, 2015 at 3:08 PM, George Dunlap
wrote:
> On Sun, Oct 4, 2015 at 12:37 PM, Bilal Bakht Ahmad
>
>>> On 14.10.15 at 11:29, wrote:
> I understand your comments above. My understanding about the gcc
> online doc is we don't need to add memory clobber when the variable
> is either an input _or_ output one. However, seems your options is
> memory clobber can be removed only
On Wed, 2015-10-14 at 09:29 +, Hu, Robert wrote:
> Hi Ian,
>
> When I now try to use standalone script for debug, it seems doesn't work
> as before. Any usage changed?
>
> [root@robert-ivt osstest]# ./standalone run-job --dry-run -h dummy test
> -amd64-amd64-qemuu-nested
> Could not open a
[ CC qemu-block ]
Am 13.10.2015 um 19:10 hat Stefano Stabellini geschrieben:
> On Tue, 13 Oct 2015, John Snow wrote:
> > On 10/13/2015 11:55 AM, Fabio Fantoni wrote:
> > > I added ahci disk support in libxl and using it for week seems that was
> > > ok, after a reply of Stefano Stabellini seems
flight 62948 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/62948/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 16
guest-localmigrate/x10 fail REGR. vs.
>>> On 14.10.15 at 11:08, wrote:
> After some thinking, just set/clear p2m->ept.ept_ad is not enough -- we
> also need to __vmwrite it to VMCS's EPTP, and then call ept_sync_domain.
Ah, yes, this makes sense of course.
> I have verified attached patch can work.
>>> On 13.10.15 at 18:18, wrote:
> El 13/10/15 a les 16.43, Jan Beulich ha escrit:
> On 13.10.15 at 15:32, wrote:
>>> --- a/tools/libxc/xc_dom_x86.c
>>> +++ b/tools/libxc/xc_dom_x86.c
>>> @@ -841,6 +841,23 @@ static int vcpu_hvm(struct xc_dom_image
On Tue, Oct 13, 2015 at 06:27:20PM +0200, Roger Pau Monne wrote:
> Xen always set the FPU as initialized when loading a HVM context, so libxc
> has to provide a valid FPU context when setting the CPU registers.
>
> This is a stop-gap measure in order to unblock OSSTest Windows 7 failures
> while
flight 38167 distros-debian-squeeze real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38167/
Perfect :-)
All tests in this flight passed
baseline version:
flight 38133
jobs:
build-amd64 pass
build-armhf
On Wed, Oct 14, 2015 at 03:40:01AM -0600, Jan Beulich wrote:
> >>> On 14.10.15 at 04:45, wrote:
> > However, patch 2 is still necessary. The existing tsc_get_info() uses
> > the host TSC frequency as the guest TSC frequency for a domain in
> > TSC_MODE_DEFAULT, which
Hi Stefano,
On 14/10/2015 18:49, Stefano Stabellini wrote:
Signed-off-by: Stefano Stabellini
---
arch/arm/xen/enlighten.c |6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/xen/enlighten.c b/arch/arm/xen/enlighten.c
index 6c09cc4..59f5421
Hi Stefano,
On 14/10/2015 16:57, Stefano Stabellini wrote:
-make -C BaseTools/Source/C
-OvmfPkg/build.sh -a X64 -b RELEASE -n 4
-cp Build/OvmfX64/RELEASE_GCC*/FV/OVMF.fd ovmf.bin
+make -C BaseTools
+
+if [[ $RAISIN_ARCH = "arm64" ]]
+then
+# Just use gcc4.8 flags
flight 62956 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/62956/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemut-win7-amd64 9 windows-installfail REGR. vs. 62711
Hi Stefano,
On 14/10/2015 18:49, Stefano Stabellini wrote:
Build cpu_hotplug for ARM and ARM64 guests.
Rename arch_(un)register_cpu to xen_(un)register_cpu and provide an
empty implementation on ARM and ARM64. On x86 just call
arch_(un)register_cpu as we are already doing.
Initialize
On Mon, 2015-10-12 at 18:32 +0100, Wei Liu wrote:
> Hi all
>
> Please express your preference with -2 (strongly argue against), -1
> (not happy but not against), +1 (happy but won't argue for) and +2
> (happy and argue for).
>
> # 6 months release cycle + current stable release scheme
>
> The
When a guest configuration list xvdX for its disks, there is no need to
provide an emulated driver for the same target.
Such configuration can work with the OVMF firmware, as it supports PV
disk.
Signed-off-by: Anthony PERARD
---
tools/libxl/libxl_dm.c | 6 ++
1
On Wed, Oct 14, 2015 at 12:25:32PM +0100, Stefano Stabellini wrote:
> Hi Wei, Anthony,
>
> the OVMF revision that we use with Xen 4.6 is
> cb9a7ebabcd6b8a49dc0854b2f9592d732b5afbd, however that doesn't work for
> arm64. It is not a problem for xen.git, because the arm64 build of ovmf
> is not
Hi Wei, Anthony,
the OVMF revision that we use with Xen 4.6 is
cb9a7ebabcd6b8a49dc0854b2f9592d732b5afbd, however that doesn't work for
arm64. It is not a problem for xen.git, because the arm64 build of ovmf
is not enabled in the xen tree (it is built separately). However it is a
problem for
On Wed, 14 Oct 2015, Kevin Wolf wrote:
> [ CC qemu-block ]
>
> Am 13.10.2015 um 19:10 hat Stefano Stabellini geschrieben:
> > On Tue, 13 Oct 2015, John Snow wrote:
> > > On 10/13/2015 11:55 AM, Fabio Fantoni wrote:
> > > > I added ahci disk support in libxl and using it for week seems that was
>
I also needed to document some of the more special runvars for
reference purposes.
Signed-off-by: Ian Campbell
---
README | 177 +
1 file changed, 177 insertions(+)
diff --git a/README b/README
index
flight 62950 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/62950/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-armhf-armhf-libvirt-xsm 7 host-ping-check-xen fail REGR. vs. 62943
test-armhf-armhf-xl-rtds
>>> On 14.10.15 at 12:03, wrote:
>
>> -Original Message-
>> From: Jan Beulich [mailto:jbeul...@suse.com]
>> Sent: Wednesday, October 14, 2015 5:46 PM
>> To: Wu, Feng
>> Cc: Andrew Cooper ; xen-devel@lists.xen.org;
>> Keir
On Fri, 2015-10-09 at 11:40 +0100, Julien Grall wrote:
> On 09/10/15 10:22, Ian Campbell wrote:
> > On Thu, 2015-10-08 at 20:22 +0100, Julien Grall wrote:
> > > When restoring the system register state for an AArch32 guest at EL2,
> > > writes to DACR32_EL2 may not be correctly synchronised by
On Wed, 2015-10-14 at 10:59 +0100, Wei Liu wrote:
> On Tue, Oct 13, 2015 at 06:27:20PM +0200, Roger Pau Monne wrote:
> > Xen always set the FPU as initialized when loading a HVM context, so
> > libxc
> > has to provide a valid FPU context when setting the CPU registers.
> >
> > This is a stop-gap
On Wed, 2015-10-14 at 10:34 +0100, Julien Grall wrote:
> The variable new_data is initialized to NULL and free but never
> allocated neither used.
>
> Signed-off-by: Julien Grall
Acked + applied.
___
Xen-devel mailing list
>>> On 13.10.15 at 10:53, wrote:
> This is the xl/xc changes to support Intel Code/Data Prioritization.
> CAT xl commands to set/get CBMs are extended to support CDP.
> Add new CDP options with CAT commands in xl interface man page.
> Add description of CDP in
On Mon, 12 Oct 2015, Wei Liu wrote:
> Hi all
>
> We've had two separate discussions about release cycles, one for
> normal release [0], the other for changes in stable release
> maintenance and possible long term supported releases [1]. There were
> overwhelming support for having a shorter
On Wed, 2015-10-14 at 12:06 +0100, Stefano Stabellini wrote:
> > Can't you just teach SeaBIOS how to deal with your PV disks and then
> > only add that to your VM and forget about IDE/AHCI? I mean, that's how
> > it's done for virtio-blk, and it doesn't involve any insanities like
> > ripping out
Am 14.10.2015 um 13:06 hat Stefano Stabellini geschrieben:
> On Wed, 14 Oct 2015, Kevin Wolf wrote:
> > [ CC qemu-block ]
> >
> > Am 13.10.2015 um 19:10 hat Stefano Stabellini geschrieben:
> > > On Tue, 13 Oct 2015, John Snow wrote:
> > > > On 10/13/2015 11:55 AM, Fabio Fantoni wrote:
> > > > > I
On Wed, 14 Oct 2015, Wei Liu wrote:
> On Wed, Oct 14, 2015 at 12:25:32PM +0100, Stefano Stabellini wrote:
> > Hi Wei, Anthony,
> >
> > the OVMF revision that we use with Xen 4.6 is
> > cb9a7ebabcd6b8a49dc0854b2f9592d732b5afbd, however that doesn't work for
> > arm64. It is not a problem for
1 - 100 of 158 matches
Mail list logo