Allow guest userspace code to request that a vm_event be sent out
via VMCALL. This functionality seems to be handy for a number of
Xen developers, as stated on the mailing list (thread "[Xen-devel]
HVMOP_guest_request_vm_event only works from guest in ring0").
Signed-off-by: Razvan Cojocaru
---
flight 100322 xen-4.5-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/100322/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemut-debianhvm-amd64 3 host-install(3) broken REGR. vs.
99752
test-amd64
Add a parameter to xencommons configuration file for specifying the
maximum memory size of the xenstore domain.
Signed-off-by: Juergen Gross
---
tools/hotplug/Linux/init.d/sysconfig.xencommons.in | 11 +++
tools/hotplug/Linux/launch-xenstore.in | 1 +
2 files changed, 12 ins
Add a parameter to specify the maximum memory size of the xenstore
domain. In case the xenstore domain supports ballooning it will be
capable to adjust its own size according to its memory needs.
The maximum memory size can be specified as an absolute value in
MiB, as a fraction of the host's memo
Support xenstore domain autoballooning by:
- adding --maxmem parameter to init-xenstore-domain
- build xenstore stubdom with Mini-OS CONFIG_BALLOON set
- add XENSTORE_MAX_DOMAIN_SIZE parameter to sysconfig.xencommons
This series requires Mini-OS ballooning support, of course. I'm posting
it now be
Compile xenstore stubdom with ballooning support.
Signed-off-by: Juergen Gross
---
stubdom/xenstore-minios.cfg | 1 +
1 file changed, 1 insertion(+)
diff --git a/stubdom/xenstore-minios.cfg b/stubdom/xenstore-minios.cfg
index 6a09cce..c89e9f0 100644
--- a/stubdom/xenstore-minios.cfg
+++ b/stubd
The system could be in the process of freeing up resources. Give it some
time to finish.
Signed-off-by: Wei Liu
---
This won't be necessary once we fix all synchronisation issues in
xtf-runner.
---
ts-leak-check | 3 +++
1 file changed, 3 insertions(+)
diff --git a/ts-leak-check b/ts-leak-check
Signed-off-by: Wei Liu
---
ap-common | 4
1 file changed, 4 insertions(+)
diff --git a/ap-common b/ap-common
index 19c7580..46523f3 100644
--- a/ap-common
+++ b/ap-common
@@ -33,6 +33,10 @@
: ${TREEVCS_LINUX:=git}
+: ${TREE_XTF:=git://xenbits.xen.org/xtf.git}
+: ${PUSH_TREE_XTF:=$XENBI
---
ap-common | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/ap-common b/ap-common
index 46523f3..e544605 100644
--- a/ap-common
+++ b/ap-common
@@ -33,9 +33,9 @@
: ${TREEVCS_LINUX:=git}
-: ${TREE_XTF:=git://xenbits.xen.org/xtf.git}
-: ${PUSH_TREE_XTF:=$XENBITS:/hom
Signed-off-by: Wei Liu
Acked-by: Ian Jackson
---
sg-run-job | 5 +
1 file changed, 5 insertions(+)
diff --git a/sg-run-job b/sg-run-job
index 259fc3b..240b265 100755
--- a/sg-run-job
+++ b/sg-run-job
@@ -480,6 +480,7 @@ proc need-hosts/build {} { return BUILD }
proc need-hosts/build-kern {
... so that other build scripts can use it, too.
It now accepts one more parameter called "component" to be useful in
other build scripts.
No functional change.
Signed-off-by: Wei Liu
---
v2: new
---
Osstest/BuildSupport.pm | 15 +++
ts-xen-build| 18 ++
Signed-off-by: Wei Liu
---
mfi-common | 29 +
1 file changed, 29 insertions(+)
diff --git a/mfi-common b/mfi-common
index 971ded3..b1e8dab 100644
--- a/mfi-common
+++ b/mfi-common
@@ -67,6 +67,21 @@ xenbranch_xsm_variants () {
esac
}
+xenbranch_wants_xtf_tests
By default FEP depends on debug flag. When we are near release the debug
flag will be turned off. In order to test a release build, we explicitly
enable FEP in build configuration.
Since we target Xen versions that already have Kconfig support, only a
Kconfig option is created for now.
We can eas
Extract XTF to the desire location.
Signed-off-by: Wei Liu
---
v2: remove reference of runvar xtfdir
---
ts-xtf-install | 37 +
1 file changed, 37 insertions(+)
create mode 100755 ts-xtf-install
diff --git a/ts-xtf-install b/ts-xtf-install
new file mode 1007
Hi all
This patch series integrates XTF into OSSTest. It still depends on
quite a few things (listed below) but I think it has gotten to point
that it can be posted for review.
It depends on having a canonical location for xtf.git. Currently this
series contains a patch to point to my own xtf.git
Clone, build and package XTF for later use.
Signed-off-by: Wei Liu
---
v2:
1. use buildcmd_stamped_logged
2. pass @ARGV to make
3. use /home/xtf
---
ts-xtf-build | 54 ++
1 file changed, 54 insertions(+)
create mode 100755 ts-xtf-build
diff -
flight 100328 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/100328/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 74bbe31b8d485da26ec7ffad5e78b8384a9eb9a5
baseline version:
ovmf 7e9cf612056ed2667eaad
On 04/08/16 09:59, Dario Faggioli wrote:
> In fact, 52cf096df7 ("xenalyze: handle scheduling event"),
> when dealing with TRC_SCHED_SWITCH, forgot to check whether
> we actually are in dump mode, causing the printf() in
> dump_sched_switch() to always produce its output, which
> is not what we want
On Thu, 2016-08-04 at 01:15 -0400, Meng Xu wrote:
> Hi Dario,
>
Hi,
> I'm thinking about changing the current RTDS scheduler to
> work-conserving version as we briefly discussed before.
> Below is a design of the work-conserving RTDS.
> I'm hoping to get your feedback about the design ideas first
On Fri, Aug 05, Olaf Hering wrote:
> Not sure what change was made to hide the error.
On the receiving side, /usr/bin/qemu-system-i386 works while
/usr/bin/qemu-system-x86_64 fails. Since the sending side is
/usr/lib/xen/bin/qemu-system-i386 there is appearenly an incompatibality
between the i386
branch xen-4.5-testing
xenbranch xen-4.5-testing
job test-amd64-amd64-xl-pvh-intel
testid xen-boot
Tree: linux git://xenbits.xen.org/linux-pvops.git
Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
Tree: qemuu git://xenb
This is the main script for running XTF. It will first perform
selftest, and then run each XTF test case as a substep.
It does the following things:
1. Run self tests for individual environment and record the result.
2. Collect tests according to available environments.
3. Run the collected test
Test the availability of FEP during runtime.
Signed-off-by: Wei Liu
---
v2:
1. use target_cmd_output_root to get output
2. die if the output is not in expected format
3. use fep test result as exit code of the script
4. remove the use of xtfdir runvar
---
ts-xtf-fep | 37 +++
Create jobs only for x86 and set host flag diverse-xtf-x86.
Signed-off-by: Wei Liu
---
make-flight | 22 ++
1 file changed, 22 insertions(+)
diff --git a/make-flight b/make-flight
index 18e5bc3..613b3d0 100755
--- a/make-flight
+++ b/make-flight
@@ -422,6 +422,26 @@ do_rtds_
This branch contains Xen and Linux build jobs and all jobs which contain
xtf in their name.
Signed-off-by: Wei Liu
---
I'm not sure if everything is ok because I can't test all changes.
---
ap-fetch-version | 4
ap-print-url | 3 +++
ap-push | 5 +
cr-daily-branch | 8
vmx_vmenter_helper is not part of the call stack. The address is simply the
location of the ud2 to which the
__vmwrite(HOST_CR0, v->arch.hvm_vmx.host_cr0);
In
static void vmx_fpu_leave(struct vcpu *v)
jumps.
There are two vmwrites in vmx_vcpu_update_eptp (called by altp2m_vcpu_destroy):
__vmwrite
Install XTF, run FEP test and then run all available tests.
Signed-off-by: Wei Liu
---
v2: spawn and reap ts-xtf-fep to make it non-fatal
---
sg-run-job | 10 ++
1 file changed, 10 insertions(+)
diff --git a/sg-run-job b/sg-run-job
index 240b265..c9773ab 100755
--- a/sg-run-job
+++ b/sg
Whether or not an error code is needed can be determinted entirely from the
trapnr paramter, as error codes are architecturally specified.
Introduce TRAP_HAVE_EC as a bitmap of reserved vectors which have error codes,
and drop the use_error_code from all callsites.
As a result, the DO_ERROR{,_NOC
xenalyze was inheriting LDLIBS of xentrace; but it doesn't need them.
Remove this dependency, which allows xenalyze to be built without the libraries
having been built, and run without the libraries being installed.
Signed-off-by: George Dunlap
---
CC: Ian Jackson
CC: Wei Liu
CC: Dario Faggiol
At the moment these structures are not used, and half of the code for
collecting it is commented out. To be used they require further
support for collecting hardware instruction counter data inside of
Xen.
Remove the code entirely; when they're wanted again they will be here
in the git log.
Sign
Rather than have large fixed-size buffers, start with smaller buffers
and allow them to grow as needed (doubling each time), with a fairly
large maximum. Allow this maximum to be set by a command-line
parameter.
Signed-off-by: George Dunlap
---
CC: Ian Jackson
CC: Wei Liu
CC: Dario Faggioli
C
The only difference between event_cycle_summary and cycle_summary was
that the former has a separate counter for "events" which had
zero-cycle events. But a lot of the code dealing with them had to be
duplicated with slightly different fields.
Remove event_cycle_summary, add an "event_count" fiel
Wei Liu writes ("Re: [RFC PATCH 8/8] tools/console: remove 5s bodge in console
client"):
> On Fri, Aug 05, 2016 at 05:36:08PM +0100, Wei Liu wrote:
> > On Fri, Aug 05, 2016 at 05:32:30PM +0100, Ian Jackson wrote:
> > > My point is that xenconsole seems to have the functionality already.
> > > You
On Fri, Aug 5, 2016 at 2:56 PM, George Dunlap wrote:
> On Thu, Aug 4, 2016 at 11:25 AM, Ian Jackson
> wrote:
>> George Dunlap writes ("[PATCH] CODING_STYLE: Allow single-sentence comments
>> without full stops"):
>>> One of the common ways in which contributors trip up over the
>>> CODING_STYLE
Wei Liu writes ("[PATCH v2 2/6] tools/console: introduce --start-notify-fd
option for console client"):
> The console client will write 0x00 to that fd before entering console
> loop to indicate its readiness.
Acked-by: Ian Jackson
> + do {
> + r = write(start_no
Wei Liu writes ("[PATCH v2 3/6] libxl: factor out libxl__console_tty_path"):
> No other user yet.
>
> Signed-off-by: Wei Liu
> Acked-by: Ian Jackson
Of course the proximate reason for this has been dropped from this
series.
However, I think this patch should be retained, because it's a step
to
Wei Liu writes ("[PATCH v2 4/6] libxl: libxl_{primary_,}console_exec now take
notify_fd argument"):
> The new argument will be passed down to xenconsole process, which then
> uses it to notify readiness.
...
> -execl(p, p, domid_s, "--num", cons_num_s, "--type", cons_type_s, (void
> *)NULL);
On Mon, Aug 08, 2016 at 11:15:01AM +0100, Ian Jackson wrote:
> Wei Liu writes ("[PATCH v2 4/6] libxl: libxl_{primary_,}console_exec now take
> notify_fd argument"):
> > The new argument will be passed down to xenconsole process, which then
> > uses it to notify readiness.
> ...
> > -execl(p, p
Wei Liu writes ("[PATCH v2 6/6] xl: use xenconsole startup protocol"):
> If user asks xl to automatically connect to console when creating a
> guest, use the new startup protocol before trying to unpause domain so
> that we don't lose any console output.
...
> if ( dom_info->console_autoconnec
And clarify that the rule about omitting braces for single statements
is optional (it is even contradicted by the example).
Signed-off-by: Ian Jackson
CC: Wei Liu
---
tools/libxl/CODING_STYLE | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/tools/libxl/CODING_STYLE b/to
Hi,
What hypercalls are available for PVH guests? How is it different for
HVM guests? Is it documented somewhere?
For example I'd expect that do_mmu_update is available only for PV
guests, but looking at the code I can't find anything preventing other
guest types from using it (no, some obscure co
>>> On 08.08.16 at 11:48, wrote:
> vmx_vmenter_helper is not part of the call stack. The address is simply the
> location of the ud2 to which the
> __vmwrite(HOST_CR0, v->arch.hvm_vmx.host_cr0);
> In
> static void vmx_fpu_leave(struct vcpu *v)
> jumps.
> There are two vmwrites in vmx_vcpu_update
Hello,
We've been mostly setting registers by using xc_vcpu_setcontext():
https://github.com/razvan-cojocaru/libbdvmi/blob/master/src/bdvmixendriver.cpp#L504
but lately trying to push as much of that as possible to the
VM_EVENT_FLAG_SET_REGISTERS-related code (i.e. via the vm_event replies)
to s
On Mon, Aug 08, 2016 at 11:21:31AM +0100, Ian Jackson wrote:
> And clarify that the rule about omitting braces for single statements
> is optional (it is even contradicted by the example).
>
> Signed-off-by: Ian Jackson
> CC: Wei Liu
Acked-by: Wei Liu
_
On Mon, Aug 08, 2016 at 11:17:20AM +0100, Ian Jackson wrote:
> Wei Liu writes ("[PATCH v2 6/6] xl: use xenconsole startup protocol"):
> > If user asks xl to automatically connect to console when creating a
> > guest, use the new startup protocol before trying to unpause domain so
> > that we don't
On Fri, Aug 05, 2016 at 06:41:32PM +0100, Wei Liu wrote:
> The new argument will be passed down to xenconsole process, which then
> uses it to notify readiness.
>
> Signed-off-by: Wei Liu
Forgot to carry over the ack from previous version.
Acked-by: Ian Jackson
I think the ack still stands
On 04/08/16 17:16, David Vrabel wrote:
> The standard return value for ioctl(2) where the cmd is not supported
> is ENOTTY, not EINVAL.
>
> Signed-off-by: David Vrabel
Reviewed-by: Juergen Gross
Juergen
___
Xen-devel mailing list
Xen-devel@lists.xe
Hi,
I'm having troubles with starting PVH guest when memory < maxmem. Exact
crash message:
(XEN) d2v0 EPT violation 0x182 (-w-/---) gpa 0x003e7ff000
mfn 0x type 4
(XEN) d2v0 Walking EPT tables for GFN 3e7ff:
(XEN) d2v0 gfn exceeds max_mapped_pfn 19000
(XE
On 08/08/16 11:21, Marek Marczykowski-Górecki wrote:
> Hi,
>
> What hypercalls are available for PVH guests?
First of all, be aware that there is currently some chaos in the
codebase which is soon to be resolved.
What you are looking for is HVMLite, which will likely be renamed to PVH
once it is
Adjusted some patches as required and pushed.
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
On Mon, Aug 08, 2016 at 10:54:28AM +0100, George Dunlap wrote:
> xenalyze was inheriting LDLIBS of xentrace; but it doesn't need them.
>
> Remove this dependency, which allows xenalyze to be built without the
> libraries
> having been built, and run without the libraries being installed.
>
> Sig
On Mon, Aug 08, 2016 at 10:54:31AM +0100, George Dunlap wrote:
> +
> +new_size = s->sample_size << 1;
> +
> +if (new_size == 0)
> +new_size = opt.sample_size;
> +
> +if (opt.sample_max != 0 && new_size > opt.sample_max)
> +new_size
On Mon, Aug 08, 2016 at 10:54:30AM +0100, George Dunlap wrote:
> The only difference between event_cycle_summary and cycle_summary was
> that the former has a separate counter for "events" which had
> zero-cycle events. But a lot of the code dealing with them had to be
> duplicated with slightly d
On Mon, Aug 08, 2016 at 10:54:29AM +0100, George Dunlap wrote:
> At the moment these structures are not used, and half of the code for
> collecting it is commented out. To be used they require further
> support for collecting hardware instruction counter data inside of
> Xen.
>
> Remove the code
Wei Liu writes ("Re: [PATCH v2 4/6] libxl: libxl_{primary_,}console_exec now
take notify_fd argument"):
> On Fri, Aug 05, 2016 at 06:41:32PM +0100, Wei Liu wrote:
> > The new argument will be passed down to xenconsole process, which then
> > uses it to notify readiness.
> >
> > Signed-off-by: Wei
On Mon, Aug 08, 2016 at 11:31:46AM +0100, Wei Liu wrote:
> On Mon, Aug 08, 2016 at 11:21:31AM +0100, Ian Jackson wrote:
> > And clarify that the rule about omitting braces for single statements
> > is optional (it is even contradicted by the example).
> >
> > Signed-off-by: Ian Jackson
> > CC: We
On Mon, Aug 08, 2016 at 12:05:58PM +0100, Wei Liu wrote:
> On Mon, Aug 08, 2016 at 10:54:31AM +0100, George Dunlap wrote:
> > +
> > +new_size = s->sample_size << 1;
> > +
> > +if (new_size == 0)
> > +new_size = opt.sample_size;
> > +
> > +if (opt.
On Tue, Aug 02, 2016 at 04:06:30PM +0200, Paulina Szubarczyk wrote:
> Copy data operated on during request from/to local buffers to/from
> the grant references.
>
> Before grant copy operation local buffers must be allocated what is
> done by calling ioreq_init_copy_buffers. For the 'read' operati
>>> On 05.08.16 at 18:28, wrote:
> Jan Beulich writes ("Re: Device model operation hypercall (DMOP, re qemu
> depriv)"):
>> On 04.08.16 at 13:21, wrote:
>> > What we cannot do is audit every HVMCTL, fix the class 2 problems, and
>> > then declare HVMCTL to have the relevant security property, an
On Mon, Aug 08, 2016 at 11:42:03AM +0100, Andrew Cooper wrote:
> On 08/08/16 11:21, Marek Marczykowski-Górecki wrote:
> > Hi,
> >
> > What hypercalls are available for PVH guests?
>
> First of all, be aware that there is currently some chaos in the
> codebase which is soon to be resolved.
>
> Wha
Now that xl create -c is fixed in xen-unstable, there is no need to keep
the hack to get guest console output anymore.
Use xl create -Fc directly, then wait for the xl process to exit. Print
any error as it occurs.
Signed-off-by: Wei Liu
---
Rebased on top of master
---
xtf-runner | 34 +++
>>> On 08.08.16 at 11:51, wrote:
> Whether or not an error code is needed can be determinted entirely from the
> trapnr paramter, as error codes are architecturally specified.
>
> Introduce TRAP_HAVE_EC as a bitmap of reserved vectors which have error codes,
> and drop the use_error_code from all
>>> On 08.08.16 at 10:06, wrote:
> Allow guest userspace code to request that a vm_event be sent out
> via VMCALL. This functionality seems to be handy for a number of
> Xen developers, as stated on the mailing list (thread "[Xen-devel]
> HVMOP_guest_request_vm_event only works from guest in ring0
On 08/08/2016 01:11 PM, Roger Pau Monné wrote:
On Tue, Aug 02, 2016 at 04:06:30PM +0200, Paulina Szubarczyk wrote:
Copy data operated on during request from/to local buffers to/from
the grant references.
Before grant copy operation local buffers must be allocated what is
done by calling ioreq_i
>>> On 08.08.16 at 12:40, wrote:
> I'm having troubles with starting PVH guest when memory < maxmem. Exact
> crash message:
>
> (XEN) d2v0 EPT violation 0x182 (-w-/---) gpa 0x003e7ff000 mfn
> 0x type 4
> (XEN) d2v0 Walking EPT tables for GFN 3e7ff:
> (XEN) d2v
Hi,
as part of a number of tasks to move Xen Project websites to https, we
investigated whether we can move our tarballs to a new Xen Project owned domain
to download tarballs. Currently tarballs are stored on
http://bits.xensource.com, which is a http site only. We do not have sufficient
cont
On 08/02/2016 04:06 PM, Paulina Szubarczyk wrote:
Copy data operated on during request from/to local buffers to/from
the grant references.
Before grant copy operation local buffers must be allocated what is
done by calling ioreq_init_copy_buffers. For the 'read' operation,
first, the qemu devi
On 08/08/16 11:31, Razvan Cojocaru wrote:
> Hello,
>
> We've been mostly setting registers by using xc_vcpu_setcontext():
>
> https://github.com/razvan-cojocaru/libbdvmi/blob/master/src/bdvmixendriver.cpp#L504
>
> but lately trying to push as much of that as possible to the
> VM_EVENT_FLAG_SET_REGI
On Mon, Aug 08, 2016 at 01:19:43PM +0200, Roger Pau Monne wrote:
> On Mon, Aug 08, 2016 at 11:42:03AM +0100, Andrew Cooper wrote:
> > On 08/08/16 11:21, Marek Marczykowski-Górecki wrote:
> > > Hi,
> > >
> > > What hypercalls are available for PVH guests?
> >
> > First of all, be aware that there i
On Mon, Aug 08, 2016 at 05:38:56AM -0600, Jan Beulich wrote:
> Indeed iirc PVHv1 and PoD are incompatible with one another,
> and I don't know any possible workaround. And then I'm not
> sure it's worth your time playing with PVHv1 in the first place.
Thanks.
--
Best Regards,
Marek Marczykowski-
flight 100341 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/100341/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 12 migrate-support-checkfail never pass
test-armhf-armhf-xl 1
This run is configured for baseline tests only.
flight 66938 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/66938/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 74bbe31b8d485da26ec7ffad5e78b8384a9eb9a5
baseline v
On Mon, 2016-08-08 at 10:54 +0100, George Dunlap wrote:
> xenalyze was inheriting LDLIBS of xentrace; but it doesn't need them.
>
> Remove this dependency, which allows xenalyze to be built without the
> libraries
> having been built, and run without the libraries being installed.
>
Which is grea
On 08/08/2016 03:01 PM, Andrew Cooper wrote:
> On 08/08/16 11:31, Razvan Cojocaru wrote:
>> Hello,
>>
>> We've been mostly setting registers by using xc_vcpu_setcontext():
>>
>> https://github.com/razvan-cojocaru/libbdvmi/blob/master/src/bdvmixendriver.cpp#L504
>>
>> but lately trying to push as mu
flight 66937 distros-debian-sid real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/66937/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-i386-sid-netboot-pvgrub 9 debian-di-install fail blocked in
66876
test-amd64-i386
On 08/08/16 12:24, Wei Liu wrote:
> Now that xl create -c is fixed in xen-unstable, there is no need to keep
> the hack to get guest console output anymore.
>
> Use xl create -Fc directly, then wait for the xl process to exit. Print
> any error as it occurs.
>
> Signed-off-by: Wei Liu
Sadly, now
On 08/08/16 12:43, Lars Kurth wrote:
> Hi,
>
> as part of a number of tasks to move Xen Project websites to https, we
> investigated whether we can move our tarballs to a new Xen Project owned
> domain to download tarballs. Currently tarballs are stored on
> http://bits.xensource.com, which is
On Mon, Aug 08, 2016 at 02:06:37PM +0100, Andrew Cooper wrote:
> On 08/08/16 12:24, Wei Liu wrote:
> > Now that xl create -c is fixed in xen-unstable, there is no need to keep
> > the hack to get guest console output anymore.
> >
> > Use xl create -Fc directly, then wait for the xl process to exit.
While AMD APM suggests that reserved MSR bits are not supposed to be
touched, it is not clear how (or whether) HW enforces this for PMU
registers. At least on some family 10h processors writes of these bits
are apparently ignored: guests (such as Linux) assume that the bits
are zero and write the M
A couple of AMD VPMU fixes
* Handle original (pre-family 15h) MSR range reserved for PMU use
* Stop reporting error back to the guest when reserved PMU MSR bits are
modified since apparently guests (Linux at least) may assume those bits
to be zero. Just make sure those bits are set/cleared prio
We need to check for older PMU MSR range when emulating MSR
accesses for PV guests.
Signed-off-by: Boris Ostrovsky
---
xen/arch/x86/traps.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/xen/arch/x86/traps.c b/xen/arch/x86/traps.c
index 767d0b0..79a3516 100644
--- a/xen/arch/x86/traps.c
+
On 05/08/16 16:35, Jan Beulich wrote:
On 04.08.16 at 17:49, wrote:
>> In general, the hooks provide flexibility when having to deal with
>> unforeseen cases, but their application should be rarely required (<
>> 10%)."
>
> But the greater flexibility of course comes with increased chances
>
On 08/08/2016 08:13 AM, Marek Marczykowski-Górecki wrote:
> Thanks for the explanation. What is the current state of HVMlite? I see
> "none" is valid value for "device_model_version" already, but if I try
> to start such guest, it fails at x86_compat call (tries to boot it as PV
> guest). I guess i
flight 100331 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/100331/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-pvops 3 host-install(3) broken REGR. vs. 99955
test-armhf-armhf-libvir
Lars Kurth writes ("Proposed plan and URL name for new VM to download xen
tarballs (ftp.xenproject.org)"):
> To fix this, the current plan of record is to
> - Copy existing tarballs to an existing or new VM
> - To expose that VM via the new public URL ftp.xenproject.org (this is
> non-browsable,
>>> On 08.08.16 at 15:41, wrote:
> --- a/xen/arch/x86/traps.c
> +++ b/xen/arch/x86/traps.c
> @@ -2903,6 +2903,7 @@ static int emulate_privileged_op(struct cpu_user_regs
> *regs)
> {
> vpmu_msr = 1;
> case MSR_AMD_FAM15H_EVNTSEL0...MSR_AMD_FAM15H_PERFCTR5:
>
Jan Beulich writes ("Re: Device model operation hypercall (DMOP, re qemu
depriv)"):
> On 05.08.16 at 18:28, wrote:
> > That is, a bug of class 2 would allow the unprivileged qemu process in
> > dom0 to cause damage to other parts of dom0.
...
> Ah, okay, I think I finally understand. [...]
>
> I
>>> On 08.08.16 at 15:41, wrote:
> While AMD APM suggests that reserved MSR bits are not supposed to be
> touched, it is not clear how (or whether) HW enforces this for PMU
> registers. At least on some family 10h processors writes of these bits
> are apparently ignored: guests (such as Linux) ass
>>> On 08.08.16 at 15:42, wrote:
> On 05/08/16 16:35, Jan Beulich wrote:
> On 04.08.16 at 17:49, wrote:
>>> In general, the hooks provide flexibility when having to deal with
>>> unforeseen cases, but their application should be rarely required (<
>>> 10%)."
>>
>> But the greater flexibility
> On 8 Aug 2016, at 14:51, Ian Jackson wrote:
>
> Lars Kurth writes ("Proposed plan and URL name for new VM to download xen
> tarballs (ftp.xenproject.org)"):
>> To fix this, the current plan of record is to
>> - Copy existing tarballs to an existing or new VM
>> - To expose that VM via the new
Lars Kurth writes ("Re: Proposed plan and URL name for new VM to download xen
tarballs (ftp.xenproject.org)"):
> I don't mind. I can ask Credativ whether that is doable from a load
> perspective. But the answer is probably yes.
If it isn't doable then moving the release tarballs load elsewhere i
On 08/08/2016 09:53 AM, Jan Beulich wrote:
On 08.08.16 at 15:41, wrote:
>> --- a/xen/arch/x86/traps.c
>> +++ b/xen/arch/x86/traps.c
>> @@ -2903,6 +2903,7 @@ static int emulate_privileged_op(struct cpu_user_regs
>> *regs)
>> {
>> vpmu_msr = 1;
>> case MS
>>> On 08.08.16 at 15:46, wrote:
> Jan Beulich writes ("Re: Device model operation hypercall (DMOP, re qemu
> depriv)"):
>> I'm having, however, a hard time imagining a class 2 bug for any
>> of the hvmop-s that are being converted by the hvmctl series:
>> These act on the target domain, so would
>>> On 08.08.16 at 16:06, wrote:
> On 08/08/2016 09:53 AM, Jan Beulich wrote:
> On 08.08.16 at 15:41, wrote:
>>> --- a/xen/arch/x86/traps.c
>>> +++ b/xen/arch/x86/traps.c
>>> @@ -2903,6 +2903,7 @@ static int emulate_privileged_op(struct cpu_user_regs
> *regs)
>>> {
>>>
On 08/08/2016 09:56 AM, Jan Beulich wrote:
On 08.08.16 at 15:41, wrote:
>> While AMD APM suggests that reserved MSR bits are not supposed to be
>> touched, it is not clear how (or whether) HW enforces this for PMU
>> registers. At least on some family 10h processors writes of these bits
>> ar
On 08/08/16 15:01, Jan Beulich wrote:
On 08.08.16 at 15:42, wrote:
>> On 05/08/16 16:35, Jan Beulich wrote:
>> On 04.08.16 at 17:49, wrote:
In general, the hooks provide flexibility when having to deal with
unforeseen cases, but their application should be rarely required (<
>>
flight 100344 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/100344/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt 5 libvirt-buildfail REGR. vs. 100341
Tests which
On 08/08/2016 02:34 PM, Jan Beulich wrote:
On 08.08.16 at 10:06, wrote:
>> Allow guest userspace code to request that a vm_event be sent out
>> via VMCALL. This functionality seems to be handy for a number of
>> Xen developers, as stated on the mailing list (thread "[Xen-devel]
>> HVMOP_guest
On Wed, Jul 27, Konrad Rzeszutek Wilk wrote:
> > Xen 4.7.20160704T103633.a492556-1.xen47
> > (XEN) Xen version 4.7.20160704T103633.a492556-1.xen47 (abuild@) (gcc (SUSE
> > Linux) 4.8.5) debug=n Mon Jul 4 12:36:33 UTC 2016
>
> Could you recompile it with debug=y?
Its attached, nothing special
Hi,
On Fri, May 13, 2016 at 11:23:29AM -0400, Konrad Rzeszutek Wilk wrote:
>On Fri, May 13, 2016 at 03:25:52PM +0100, M A Young wrote:
>> On Fri, 13 May 2016, Jan Beulich wrote:
>>
>> > >>> On 13.05.16 at 15:49, wrote:
>> > > ...
>> > >
>> > > Still an issue - with 4.7.0-rc1.
>> >
>> > And I d
1 - 100 of 181 matches
Mail list logo
