On Wed, Jul 22, 2015 at 12:23:46PM -0700, Andy Lutomirski wrote:
> modify_ldt has questionable locking and does not synchronize
> threads. Improve it: redesign the locking and synchronize all
> threads' LDTs using an IPI on all modifications.
>
> This will dramatically slow down modify_ldt in mul
Hi,
I want to run an Android with xen on ARM. I use the Arndale 5250 with
Cortex-A15. But I can only boot a linux system, but can't run an Android
successfully. So I want to know if there is a guide to let me know how to boot
an Android on Xen successfully.
Also, I am doing research about xe
Hi,
When creating HVM guest(no balloon driver), what's the max memory we could set?
We can get the current system free memory by "xl info", but when configure the
free memory to a HVM guest, it fail to boot up. Does Xen allocate additional
memory when do VM creating? How many the additional me
On 07/23/2015 09:08 PM, Greg KH wrote:
On Thu, Jul 23, 2015 at 08:46:17AM +0200, Juergen Gross wrote:
On 07/23/2015 06:36 AM, Greg KH wrote:
On Thu, Jul 23, 2015 at 06:04:39AM +0200, Juergen Gross wrote:
On 07/23/2015 01:46 AM, Greg KH wrote:
On Tue, Jun 23, 2015 at 08:53:23AM +0200, Juergen
flight 59836 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/59836/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-xsm 13 guest-saverestore fail REGR. vs. 59254
test-amd64-i386-xl
> -Original Message-
> From: Dario Faggioli [mailto:dario.faggi...@citrix.com]
> Sent: Thursday, July 23, 2015 8:50 PM
> To: Wu, Feng
> Cc: xen-devel@lists.xen.org; Tian, Kevin; Keir Fraser; George Dunlap; Andrew
> Cooper; Jan Beulich
> Subject: Re: [Xen-devel] [v4 16/17] vmx: Add some sc
> -Original Message-
> From: Andrew Cooper [mailto:andrew.coop...@citrix.com]
> Sent: Thursday, July 23, 2015 9:52 PM
> To: Wu, Feng; xen-devel@lists.xen.org
> Cc: Zhang, Yang Z; Tian, Kevin; Keir Fraser; Jan Beulich
> Subject: Re: [v4 11/17] vt-d: Add API to update IRTE when VT-d PI is u
> -Original Message-
> From: Andrew Cooper [mailto:andrew.coop...@citrix.com]
> Sent: Thursday, July 23, 2015 10:05 PM
> To: Wu, Feng; xen-devel@lists.xen.org
> Cc: Tian, Kevin; Jan Beulich
> Subject: Re: [Xen-devel] [v4 04/17] iommu: Add iommu_intpost to control VT-d
> Posted-Interrupts
> -Original Message-
> From: Julien Grall [mailto:julien.gr...@citrix.com]
> Sent: Thursday, July 23, 2015 7:54 PM
> To: Wu, Feng; xen-devel@lists.xen.org
> Cc: Stefano Stabellini; Ian Campbell; Tim Deegan
> Subject: Re: [Xen-devel] [v4 15/17] arm: add a dummy arch hooks for scheduler
>
On Thu, Jul 23, 2015 at 4:58 PM, Willy Tarreau wrote:
> On Thu, Jul 23, 2015 at 04:40:14PM -0700, Andy Lutomirski wrote:
>> On Thu, Jul 23, 2015 at 4:36 PM, Kees Cook wrote:
>> > I've been pondering something like this that is even MORE generic, for
>> > any syscall. Something like a "syscalls" d
On Thu, Jul 23, 2015 at 04:40:14PM -0700, Andy Lutomirski wrote:
> On Thu, Jul 23, 2015 at 4:36 PM, Kees Cook wrote:
> > I've been pondering something like this that is even MORE generic, for
> > any syscall. Something like a "syscalls" directory under
> > /proc/sys/kernel, with 1 entry per syscal
On Thu, Jul 23, 2015 at 4:36 PM, Kees Cook wrote:
> On Thu, Jul 23, 2015 at 3:24 AM, Willy Tarreau wrote:
>> #ifdef CONFIG_SMP
>> static void flush_ldt(void *current_mm)
>> {
>> @@ -254,6 +260,9 @@ asmlinkage int sys_modify_ldt(int func, void __user *ptr,
>> {
>> int ret = -ENOSYS;
>>
On Thu, Jul 23, 2015 at 3:24 AM, Willy Tarreau wrote:
> Hi Andy,
>
> On Wed, Jul 22, 2015 at 12:23:47PM -0700, Andy Lutomirski wrote:
>> The modify_ldt syscall exposes a large attack surface and is
>> unnecessary for modern userspace. Make it optional.
>
> Wouldn't you prefer something like this
On Thu, Jul 23, 2015 at 12:08:01PM -0700, Greg KH wrote:
>
> Somewhere that people can refer to that describes this public-facing API
> that "must not ever be broken or changed". If you want to put it in a
> documentation file, or a .h file, I don't care.
>
> > >>It is used e.g. in SUSE's xen ke
flight 59832 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/59832/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-freebsd10-i386 12 guest-saverestore fail REGR. vs. 59059
test-amd64-amd64-xl
On Mon, Feb 23, 2015 at 3:25 AM, Kevin Wolf wrote:
> Am 11.02.2015 um 04:51 hat Shailesh Kumar geschrieben:
>> Hi,
>>
>> I am implementing read equivalent routine in qemu. Can some one
>> help me understand control flow of the qemu read/write
>> implementation.
>>
>> I am using xen-4.2.0 and
On 07/23/2015 06:12 PM, Wei Liu wrote:
> Hi all
>
> As I understand it most pending issues of this series are minor and the
> final day for committing is tomorrow. Checking this series in as-is is
> going to create some technical debt that either maintainers or Intel
> developers need to pay back
On Thu, Jul 23, 2015 at 12:01 AM, Ed White wrote:
> +int p2m_destroy_altp2m_by_id(struct domain *d, unsigned int idx)
> +{
> +struct p2m_domain *p2m;
> +int rc = -EINVAL;
> +
> +if ( !idx || idx > MAX_ALTP2M )
> +return rc;
> +
> +domain_pause_except_self(d);
> +
> +alt
On Thu, Jul 23, 2015 at 08:46:17AM +0200, Juergen Gross wrote:
> On 07/23/2015 06:36 AM, Greg KH wrote:
> >On Thu, Jul 23, 2015 at 06:04:39AM +0200, Juergen Gross wrote:
> >>On 07/23/2015 01:46 AM, Greg KH wrote:
> >>>On Tue, Jun 23, 2015 at 08:53:23AM +0200, Juergen Gross wrote:
> Add the defi
Ian Campbell writes ("[PATCH] target_run_apt: Correctly escape line wrapping"):
> Otherwise the envvars are on the preceding line and therefore not set
> in the apt-get process.
>
> I broke this in 6fea4be08306 "apt: lock osstest's usages of apt-get
> against each other", committed in January.
Ac
Wei Liu writes ("Re: [PATCH] libxc: Expose xc_reserved_device_memory_map to ARM
too"):
> On Thu, Jul 23, 2015 at 05:47:09PM +0100, Julien Grall wrote:
> > The commit 25652f2 "tools/libxl: detect and avoid conflicts with RDM"
> > introduced the usage of xc_reserved_device_memory_map in the libxl
>
Use restrictflight_arg in both these functions. They still use
$maxflight directly, passing it to report_blessingscond; that will
change in a moment.
No functional change.
Signed-off-by: Ian Jackson
---
sg-report-flight |4 ++--
sg-report-job-history |4 ++--
2 files changed, 4 in
Here are:
6 tiny patches which, together, centralise the handling of --max-flight=
1 tiny patch to introduce --excluded-flights=F1,F2...
1 fix to cs-bisection-step (relevant for qemu-mainline right now)
2 small patches to slightly improve job history
__
We have $maxflight in Osstest::Executive now, set appropriately.
Use that in report_blessingscond and all its callers including
report_find_push_age_info and hence in mg-all-branch-statuses and
sg-report-flight and sg-report-job-history.
No functional change.
Signed-off-by: Ian Jackson
---
Oss
Use restrictflight_arg and restrictflight_cond.
This entails replacing $maxflight_cond (which is empty or contains a
series of texts each starting with AND) with $restrictflight_cond
(which is actually an expression, and might be just "TRUE").
No functional change.
Signed-off-by: Ian Jackson
--
Abolish $maxflight. All the users outside Osstest::Executive have
been eliminated, so this is fine. Replace it with
$restrictflight_cond, which can accumulate multiple conditions.
There is a minor functional change: when multiple --max-flight options
are specified, _all_ of them take effect (eff
To reproduce a recent bisection problem I needed to exclude not just
all flights after a certain number, but also one earlier flight. So I
invented this option (and associated yaks).
Signed-off-by: Ian Jackson
---
Osstest/Executive.pm |4
1 file changed, 4 insertions(+)
diff --git a/O
There was a half-implemented memoisation. Memoisation is necessary
because otherwise the algorithm is exponential in the commit history
depth (with base equal to the commit parent fanout).
Sort this out:
* Break out the actual computation into a ne
search_compute_length_at_intern
* Deleting
Provide the new functions which we will eventually use everywhere.
* Introduce restrictflight_arg which can be used in an argument loop.
* Introduce restrictflight_cond which generates a SQL condition.
* Have restrictflight_cond's value include surrounding ( ) for safety.
* Use the above in sg-rep
We are going to move the interpretation of --max-flight into
Osstest::Executive. Start this by making $maxflight shared between
Executive and the main program. Later, we will make it no longer
exported.
There are a number of places in Executive where a `my' variable
$maxflight shadows the newly
No functional change.
Signed-off-by: Ian Jackson
---
Osstest/Executive.pm | 12
sg-report-job-history | 10 +++---
2 files changed, 15 insertions(+), 7 deletions(-)
diff --git a/Osstest/Executive.pm b/Osstest/Executive.pm
index 998a0d0..79d433a 100644
--- a/Osstest/Executi
Signed-off-by: Ian Jackson
---
sg-report-job-history |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/sg-report-job-history b/sg-report-job-history
index 11fdaaf..9a6e17b 100755
--- a/sg-report-job-history
+++ b/sg-report-job-history
@@ -232,6 +232,7 @@ END
my $a
On Thu, Jul 23, 2015 at 12:26:20PM +0100, Ian Campbell wrote:
> On Thu, 2015-07-23 at 13:17 +0200, Roger Pau Monné wrote:
> > El 23/07/15 a les 12.59, Konrad Rzeszutek Wilk ha escrit:
> > [...]
> > > We forgot to speak about dom0. This work outlined will lay out how
> > > to do it - but the pieces
On Thu, Jul 23, 2015 at 06:01:45PM +0100, Andrew Cooper wrote:
> On 23/07/15 17:35, Elena Ufimtseva wrote:
> > Hi
> >
> > While working on bugs during boot time on large oracle server x4-8,
> > There is a problem with booting Xen on large machines with > 4TB memory,
> > such as Oracle x4-8.
> > The
On Thu, Jul 23, 2015 at 01:17:45PM +0200, Roger Pau Monné wrote:
> El 23/07/15 a les 12.59, Konrad Rzeszutek Wilk ha escrit:
> [...]
> > We forgot to speak about dom0. This work outlined will lay out how to do it
> > - but the pieces for dom0 are not implemented and would need work (which
> > act
Ian Campbell 於 西元2015年07月21日 23:10 寫道:
On Fri, 2015-07-17 at 00:15 +0800, Ting-Wei Lan wrote:
This all looks pretty good. One comment:
+if test "x$qemu_xen_path" = "x" || test "x$qemu_xen_path" = "xqemu";
then :
+
+qemu_xen_path_service="$LIBEXEC_BIN/qemu-system-i386"
It's a shame we hav
On Thu, Jul 23, 2015 at 05:47:09PM +0100, Julien Grall wrote:
> The commit 25652f2 "tools/libxl: detect and avoid conflicts with RDM"
> introduced the usage of xc_reserved_device_memory_map in the libxl
> generic code. But the function is only defined for x86 which breaks the
> ARM build.
>
> The
The device model is going to restrict its xenstore connection to $DOMID
level, using XS_RESTRICT, only implemented by oxenstored at present.
Let qemu-xen access
/local/domain/$LIBXL_TOOLSTACK_DOMID/device-model/$DOMID, as it is
required by QEMU to read/write the physmap. It doesn't contain any
inf
Check whether QEMU supports the xsrestrict option, by parsing its --help
output. Store the result on xenstore for future reference on a per QEMU
binary basis, so that device_model_override still works fine with it.
Replace / with _ in the QEMU binary path before writing it to xenstore,
so that it
Starts a second QEMU to provide PV backends in userspace to HVM guests.
Use both dcs->dmss.pvqemu and dcs->dmss.dm to keep track of the starting
QEMUs. Introduce two new fields to struct libxl__dm_spawn_state: dcs to
store the pointer to libxl__domain_create_state, and rc to store the
return code.
Change the QEMU xenstore watch path to
/local/domain/$LIBXL_TOOLSTACK_DOMID/device-model/$DOMID/$EMULATOR_ID.
Currently two emulator_ids are statically allocated: one for device models and
one for pv qemus.
Add a parameter to libxl__device_model_xs_path to distinguish the device
model from the pv
Change the qdisk-backend-pid path on xenstore from
libxl/$DOMID/qdisk-backend-pid to /local/domain/$DOMID/image/pvqemu-pid to be
more similar to the device-model path.
Signed-off-by: Stefano Stabellini
---
Changes in v4:
- update xenstore-paths.markdown
---
docs/misc/xenstore-paths.markdown |
When QEMU restricts its xenstore connection, it cannot provide PV
backends. A separate QEMU instance is required to provide PV backends in
userspace, such as qdisk. With two separate instances, it is not
possible to take advantage of vkb for mouse and keyboard, as the QEMU
that emulates the graphic
Hi all,
this patch series changes libxl to start QEMU as device model with the
new xsrestrict option (http://marc.info/?l=xen-devel&m=143341692707358).
It also starts a second QEMU to provide PV backends in userspace (qdisk)
to HVM guests.
Changes in v5:
- improve commit messages with security d
Hi Stefano,
On 16/07/15 16:11, Stefano Stabellini wrote:
> On Thu, 9 Jul 2015, Julien Grall wrote:
>> All the usage of the field pfn are done using the same idiom:
>>
>> pfn_to_page(grant->pfn)
>>
>> This will return always the same page. Store directly the page in the
>> grant to clean up the co
Hello,
Please let me know if you have some information about issue below.
I created a channel device for PV guest using
channel= ["connection=pty, name=xen.channel.0,
path=/var/lib/xen/ctl-socket","connection=socket, name=xen.channel.1,
path=/var/lib/xen/ctl-socket-data"]
Xen toolsta
On Fri, 3 Jul 2015, Ian Campbell wrote:
> On Tue, 2015-06-30 at 16:00 +0100, Stefano Stabellini wrote:
> > When I made this change, I gave a careful look both at the libxl side
> > and the QEMU side. Indeed I would appreciate a second pair of eyes on
> > this. These are my observations:
>
> I thin
Hi all
As I understand it most pending issues of this series are minor and the
final day for committing is tomorrow. Checking this series in as-is is
going to create some technical debt that either maintainers or Intel
developers need to pay back in the future (and Intel has signed up for
that, th
On 23/07/15 17:56, Roger Pau Monné wrote:
> El 23/07/15 a les 18.19, Jan Beulich ha escrit:
> On 23.07.15 at 18:15, wrote:
>>> On 23/07/15 17:00, Ian Campbell wrote:
On Thu, 2015-07-23 at 17:48 +0200, Roger Pau Monné wrote:
> El 23/07/15 a les 17.32, Jan Beulich ha escrit:
> O
Try to use "xen-qemudepriv-domid$domid" first, then
"xen-qemudepriv-shared" and root if everything else fails.
The uids need to be manually created by the user or, more likely, by the
xen package maintainer.
Expose a device_model_user setting in libxl_domain_build_info, so that
opinionated caller
El 23/07/15 a les 18.49, Andrew Cooper ha escrit:
> On 23/07/15 17:19, Jan Beulich wrote:
> On 23.07.15 at 18:15, wrote:
>>> On 23/07/15 17:00, Ian Campbell wrote:
On Thu, 2015-07-23 at 17:48 +0200, Roger Pau Monné wrote:
> El 23/07/15 a les 17.32, Jan Beulich ha escrit:
> On
On Thu, 9 Jul 2015, Ian Campbell wrote:
> On Wed, 2015-07-01 at 13:50 +0100, Stefano Stabellini wrote:
>
> > @@ -878,6 +908,33 @@ static char **
> > libxl__build_device_model_args_new(libxl__gc *gc,
> > default:
> > break;
> > }
> > +
> > +if (b_info->device
On Thu, 2015-07-23 at 17:04 +0100, Wei Liu wrote:
> On Thu, Jul 23, 2015 at 09:49:49AM -0600, Jan Beulich wrote:
> > >>> On 23.07.15 at 16:45, wrote:
> > > Dario Faggioli (2):
> > > xen: sched: reorganize cpu_disable_scheduler()
> > > xen: sched/cpupool: properly update affinity when
On 23/07/15 17:35, Elena Ufimtseva wrote:
> Hi
>
> While working on bugs during boot time on large oracle server x4-8,
> There is a problem with booting Xen on large machines with > 4TB memory,
> such as Oracle x4-8.
> The page fault occured initially while loading xen pm info into hypervisor
> (yo
El 23/07/15 a les 18.19, Jan Beulich ha escrit:
On 23.07.15 at 18:15, wrote:
>> On 23/07/15 17:00, Ian Campbell wrote:
>>> On Thu, 2015-07-23 at 17:48 +0200, Roger Pau Monné wrote:
El 23/07/15 a les 17.32, Jan Beulich ha escrit:
On 23.07.15 at 17:10, wrote:
>> IMHO introduc
>From: Jan Beulich [mailto:jbeul...@suse.com]
>Sent: Thursday, July 23, 2015 9:09 AM
>
On 23.07.15 at 01:01, wrote:
>> --- a/xen/arch/x86/hvm/hvm.c
>> +++ b/xen/arch/x86/hvm/hvm.c
>> @@ -6005,6 +6005,9 @@ static int hvmop_set_param(
>> nestedhvm_vcpu_destroy(v);
>> b
Introduce a raisin build test to OSSTest. The build is meant to test
Raisin itself.
Enable the raisin build just for xen-unstable. Disable it for all the
older Xen branches and for all the non-Xen branches.
The components built by the raisin job are static; the list is written
by ts-raisin-build.
Determine the most recent raisin revision that needs to be tested, by comparing
the staging with the master branches. Push to raisin.git:master when the build
is successful.
Do not run any jobs on the raisin flight.
Signed-off-by: Stefano Stabellini
---
Changes in v8:
- add raisin to BRANCHES
Hi all,
the first patch introduces a Raisin build job, meant to test Raisin
itself. The second patch push-gates Raisin on successful builds.
Signed-off-by: Stefano Stabellini
Changes in v8:
- update commit message
- do not install-builddep in ts-raisin-build, rely on ts-xen-build-dep
- add rai
>From: Jan Beulich [mailto:jbeul...@suse.com]
>Sent: Thursday, July 23, 2015 9:16 AM
>
On 23.07.15 at 18:08, wrote:
>> On 07/23/2015 03:51 PM, Sahita, Ravi wrote:
> +int p2m_destroy_altp2m_by_id(struct domain *d, unsigned int idx) {
> +struct p2m_domain *p2m;
> +int rc = -
Hi Chris,
Thank you for patch.
On 23/07/15 17:31, Chris (Christopher) Brand wrote:
> In setup_mm(), the value passed as xenheap_megabytes gets
> converted to pages and passed to setup_xenheap_mappings(),
> which in turn passes it to create_32mb_mappings(), which
> contains an ASSERT that the valu
On 23/07/15 17:19, Jan Beulich wrote:
On 23.07.15 at 18:15, wrote:
>> On 23/07/15 17:00, Ian Campbell wrote:
>>> On Thu, 2015-07-23 at 17:48 +0200, Roger Pau Monné wrote:
El 23/07/15 a les 17.32, Jan Beulich ha escrit:
On 23.07.15 at 17:10, wrote:
>> IMHO introducing a new
The commit 25652f2 "tools/libxl: detect and avoid conflicts with RDM"
introduced the usage of xc_reserved_device_memory_map in the libxl
generic code. But the function is only defined for x86 which breaks the
ARM build.
The hypercall called by this helper is implemented in the generic code
and doe
On Thu, Jul 23, 2015 at 05:16:45PM +0100, Ian Campbell wrote:
> On Wed, 2015-07-22 at 11:13 +0100, Wei Liu wrote:
> > +++ b/Osstest/Toolstack/libvirt.pm
> > [...]
> > +sub saverestore_check ($) {
> > +my ($self) = @_;
> > +return check_for_command($self, "save");
>
> I just noticed that in
Jan Beulich 於 西元2015年07月21日 15:33 寫道:
On 21.07.15 at 09:23, wrote:
From: Jan Beulich [mailto:jbeul...@suse.com]
Sent: Tuesday, July 21, 2015 3:17 PM
On 21.07.15 at 09:05, wrote:
From: Jan Beulich [mailto:jbeul...@suse.com]
Sent: Tuesday, July 21, 2015 2:57 PM
On 21.07.15 at 02:57, wr
On Thu, Jul 23, 2015 at 09:49:49AM -0600, Jan Beulich wrote:
> >>> On 23.07.15 at 16:45, wrote:
> > Take 4, with "only" typos and language fixes in comments, in patch 1.
> >
> > This now have all the Ack-s it requires, I think.
>
> So it does.
>
> > Dario Faggioli (2):
> > xen: sched: reo
In setup_mm(), the value passed as xenheap_megabytes gets
converted to pages and passed to setup_xenheap_mappings(),
which in turn passes it to create_32mb_mappings(), which
contains an ASSERT that the value passed is a multiple of
32MB. So specifying any value that is not an integer multiple
of 32
On Wed, 2015-07-22 at 11:13 +0100, Wei Liu wrote:
> Since upstream QEMU is the default, that's what libvirt is using. We
> generate test case to test libvirt with upstream QEMU.
>
> Signed-off-by: Wei Liu
Acked-by: Ian Campbell
___
Xen-devel mailing
On Wed, 2015-07-22 at 11:13 +0100, Wei Liu wrote:
> +++ b/Osstest/Toolstack/libvirt.pm
> [...]
> +sub saverestore_check ($) {
> +my ($self) = @_;
> +return check_for_command($self, "save");
I just noticed that in a later patch you parse the capabilities xml to
check for migration support.
On Wed, 2015-07-22 at 11:13 +0100, Wei Liu wrote:
> Since we've introduced different checks for save / restore and local
> migration, it's possible to run save / restore tests without running
> local migration tests.
>
> Signed-off-by: Wei Liu
I think at this point libvirt still fails, just late
On Wed, 2015-07-22 at 11:13 +0100, Wei Liu wrote:
> Libvirt's configuration converter doesn't know how to deal with BIOS
> selection. The end result is it always use the default one (seabios).
> Stub out ovmf and rombios to avoid false positive results.
>
> This restriction will be removed once li
On Thu, 2015-07-23 at 10:11 -0600, Jan Beulich wrote:
> >
> > > > On 23.07.15 at 17:59, wrote:
> > On Thu, 2015-07-23 at 09:37 -0600, Jan Beulich wrote:
> > > >
> > > > It's marked as experimental, not supported and not built by
> > > > default
> > > > --
> > > > if that makes you feel more co
On Wed, 2015-07-22 at 11:13 +0100, Wei Liu wrote:
> Setting kernel to hvmloader is ignored in xl but not in libvirt.
> Libvirt
> config converter will translate that then pass it to QEMU. QEMU
> complains there is no kernel called hvmloader and exits.
>
> Remove this option for xl and libvirt. X
>>> On 23.07.15 at 18:15, wrote:
> On 23/07/15 17:00, Ian Campbell wrote:
>> On Thu, 2015-07-23 at 17:48 +0200, Roger Pau Monné wrote:
>>> El 23/07/15 a les 17.32, Jan Beulich ha escrit:
>>> On 23.07.15 at 17:10, wrote:
> IMHO introducing a new structure that gets rid of all the PV-only
>>> On 23.07.15 at 18:08, wrote:
> On 07/23/2015 03:51 PM, Sahita, Ravi wrote:
+int p2m_destroy_altp2m_by_id(struct domain *d, unsigned int idx) {
+struct p2m_domain *p2m;
+int rc = -EINVAL;
+
+if ( !idx || idx > MAX_ALTP2M )
>>>
>>> >= (and then also elsew
On Wed, 2015-07-22 at 11:13 +0100, Wei Liu wrote:
>
> +# Mode should be either 1 ("local") or 0 ("remote")
> +our ($whhost, $gn, $mode) = @ARGV;
I think $mode would be better given a more "boolean" name, in this case
$local.
However that's a minor nit so with or without that changed:
Acked-by:
On 23/07/15 17:00, Ian Campbell wrote:
> On Thu, 2015-07-23 at 17:48 +0200, Roger Pau Monné wrote:
>> El 23/07/15 a les 17.32, Jan Beulich ha escrit:
>> On 23.07.15 at 17:10, wrote:
IMHO introducing a new structure that gets rid of all the PV-only
fields seems like a good optio
On Wed, 2015-07-22 at 11:13 +0100, Wei Liu wrote:
> We need this script because we're going to separate the concept of
> save
> / restore and migration later.
>
> Signed-off-by: Wei Liu
Acked-by: Ian Campbell
___
Xen-devel mailing list
Xen-devel@li
On 23/07/15 17:00, Jan Beulich wrote:
On 23.07.15 at 17:55, wrote:
>> On 23/07/15 16:52, Jan Beulich wrote:
>> On 23.07.15 at 15:51, wrote:
On 23/07/15 12:35, Feng Wu wrote:
> +GET_IREMAP_ENTRY(ir_ctrl->iremap_maddr, remap_index, iremap_entries,
> p);
> +
> +
>>> On 23.07.15 at 17:59, wrote:
> On Thu, 2015-07-23 at 09:37 -0600, Jan Beulich wrote:
>> >
>> > It's marked as experimental, not supported and not built by default
>> > --
>> > if that makes you feel more comfortable.
>>
>> It does. So Ian, feel free to go ahead.
>
> Thanks. I suppose you w
On Wed, 2015-07-22 at 11:13 +0100, Wei Liu wrote:
> Introduce check_for_command function and use it to check save /
> restore
> functionality.
>
> Signed-off-by: Wei Liu
Acked-by: Ian Campbell
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http
On 07/23/2015 03:51 PM, Sahita, Ravi wrote:
>>> +int p2m_destroy_altp2m_by_id(struct domain *d, unsigned int idx) {
>>> +struct p2m_domain *p2m;
>>> +int rc = -EINVAL;
>>> +
>>> +if ( !idx || idx > MAX_ALTP2M )
>>
>> >= (and then also elsewhere further down)?
>>
>
> Right.
[snip]
>>> On 23.07.15 at 01:01, wrote:
> --- a/xen/arch/x86/hvm/hvm.c
> +++ b/xen/arch/x86/hvm/hvm.c
> @@ -6005,6 +6005,9 @@ static int hvmop_set_param(
> nestedhvm_vcpu_destroy(v);
> break;
> case HVM_PARAM_ALTP2M:
> +rc = xsm_hvm_param_altp2mhvm(XSM_PRIV, d);
> +
Otherwise the envvars are on the preceding line and therefore not set
in the apt-get process.
I broke this in 6fea4be08306 "apt: lock osstest's usages of apt-get
against each other", committed in January.
Signed-off-by: Ian Campbell
---
Osstest/TestSupport.pm | 2 +-
1 file changed, 1 insertion
>>> On 23.07.15 at 17:55, wrote:
> On 23/07/15 16:52, Jan Beulich wrote:
> On 23.07.15 at 15:51, wrote:
>>> On 23/07/15 12:35, Feng Wu wrote:
+GET_IREMAP_ENTRY(ir_ctrl->iremap_maddr, remap_index, iremap_entries,
p);
+
+old_ire = new_ire = *p;
+
+/* S
On Thu, 2015-07-23 at 17:48 +0200, Roger Pau Monné wrote:
> El 23/07/15 a les 17.32, Jan Beulich ha escrit:
> > > > > On 23.07.15 at 17:10, wrote:
> > > IMHO introducing a new structure that gets rid of all the PV-only
> > >
> > > fields seems like a good option:
> > >
> > > struct vcpu_hvm_con
On Thu, 2015-07-23 at 09:37 -0600, Jan Beulich wrote:
> >
> > It's marked as experimental, not supported and not built by default
> > --
> > if that makes you feel more comfortable.
>
> It does. So Ian, feel free to go ahead.
Thanks. I suppose you were addressing Ian J here since I don't
typica
>>> On 23.07.15 at 17:48, wrote:
> El 23/07/15 a les 17.32, Jan Beulich ha escrit:
> On 23.07.15 at 17:10, wrote:
>>> IMHO introducing a new structure that gets rid of all the PV-only
>>> fields seems like a good option:
>>>
>>> struct vcpu_hvm_context {
>>> #define _VGCF_online
On 23/07/15 16:52, Jan Beulich wrote:
On 23.07.15 at 15:51, wrote:
>> On 23/07/15 12:35, Feng Wu wrote:
>>> +GET_IREMAP_ENTRY(ir_ctrl->iremap_maddr, remap_index, iremap_entries,
>>> p);
>>> +
>>> +old_ire = new_ire = *p;
>>> +
>>> +/* Setup/Update interrupt remapping table entry.
>>> On 23.07.15 at 15:51, wrote:
> On 23/07/15 12:35, Feng Wu wrote:
>> +GET_IREMAP_ENTRY(ir_ctrl->iremap_maddr, remap_index, iremap_entries, p);
>> +
>> +old_ire = new_ire = *p;
>> +
>> +/* Setup/Update interrupt remapping table entry. */
>> +setup_posted_irte(&new_ire, pi_desc, g
El 23/07/15 a les 17.32, Jan Beulich ha escrit:
On 23.07.15 at 17:10, wrote:
>> IMHO introducing a new structure that gets rid of all the PV-only
>> fields seems like a good option:
>>
>> struct vcpu_hvm_context {
>> #define _VGCF_online 5
>> #define VGCF_online
>>> On 23.07.15 at 16:45, wrote:
> Take 4, with "only" typos and language fixes in comments, in patch 1.
>
> This now have all the Ack-s it requires, I think.
So it does.
> Dario Faggioli (2):
> xen: sched: reorganize cpu_disable_scheduler()
> xen: sched/cpupool: properly update aff
>>> On 23.07.15 at 17:31, wrote:
> On Thu, Jul 23, 2015 at 09:28:15AM -0600, Jan Beulich wrote:
>> >>> On 23.07.15 at 16:58, wrote:
>> > On Thu, 2015-07-23 at 08:51 -0600, Jan Beulich wrote:
>> >> >
>> >> > > > On 23.07.15 at 16:43, wrote:
>> >> > On Thu, 2015-07-23 at 08:26 -0600, Jan Beulich
>>> On 23.07.15 at 17:10, wrote:
> IMHO introducing a new structure that gets rid of all the PV-only
> fields seems like a good option:
>
> struct vcpu_hvm_context {
> #define _VGCF_online 5
> #define VGCF_online(1<<_VGCF_online)
> uint32_t flags;
On Thu, Jul 23, 2015 at 09:28:15AM -0600, Jan Beulich wrote:
> >>> On 23.07.15 at 16:58, wrote:
> > On Thu, 2015-07-23 at 08:51 -0600, Jan Beulich wrote:
> >> >
> >> > > > On 23.07.15 at 16:43, wrote:
> >> > On Thu, 2015-07-23 at 08:26 -0600, Jan Beulich wrote:
> >> > > >
> >> > > > > > On 23.0
>>> On 23.07.15 at 16:58, wrote:
> On Thu, 2015-07-23 at 08:51 -0600, Jan Beulich wrote:
>> >
>> > > > On 23.07.15 at 16:43, wrote:
>> > On Thu, 2015-07-23 at 08:26 -0600, Jan Beulich wrote:
>> > > >
>> > > > > > On 23.07.15 at 15:56, wrote:
>> > > > The version of OVMF in 4.5 (and presumably
>From: Jan Beulich [mailto:jbeul...@suse.com]
>Sent: Thursday, July 23, 2015 8:09 AM
>
On 23.07.15 at 16:56, wrote:
>>> From: Jan Beulich [mailto:jbeul...@suse.com]
>>>Sent: Thursday, July 23, 2015 3:22 AM
>>>
>> On 23.07.15 at 01:01, wrote:
Signed-off-by: Ed White
Acked-
On Thu, 2015-07-23 at 17:09 +0200, Martin Lucina wrote:
> > But maybe it would be better to set max_fd = -1 on declaration and
> > do
> > the max dance here as with the following cases?
>
> Declaring max_fd = -1 is indeed clearer, I can do a v2 with that
> change if you like.
If you are happy
El 23/07/15 a les 13.41, Ian Campbell ha escrit:
> On Thu, 2015-07-23 at 05:29 -0600, Jan Beulich wrote:
>>>
> On 23.07.15 at 12:25, wrote:
>>> El 13/07/15 a les 16.01, Jan Beulich ha escrit:
>>> On 03.07.15 at 13:34, wrote:
> --- a/xen/arch/x86/domain.c
> +++ b/xen/arch/x86/domai
>>> On 23.07.15 at 16:56, wrote:
>> From: Jan Beulich [mailto:jbeul...@suse.com]
>>Sent: Thursday, July 23, 2015 3:22 AM
>>
> On 23.07.15 at 01:01, wrote:
>>> Signed-off-by: Ed White
>>>
>>> Acked-by: Jan Beulich
>>
>>And I have to withdraw this ack pending clarification of (and perhaps
>>a
1 - 100 of 275 matches
Mail list logo
