On Wed, Aug 24, 2016 at 01:51:13AM -0600, Jan Beulich wrote:
> Non-debugging message text should be (and is in the cases here)
> distinguishable without also logging function names. Additionally log
> the PCI device coordinates for alloc_pdev() failure.
>
Reviewed-by: Konrad Rzeszutek Wilk
> Sig
On Wed, Aug 24, 2016 at 01:54:08AM -0600, Jan Beulich wrote:
> Debugging message text already includes file name and line number, so
> also logging function names is redundant.
And you also fixed one style guide violation :-)
>
> Signed-off-by: Jan Beulich
Reviewed-by: Konrad Rzeszutek Wilk
_
On Wed, Aug 24, 2016 at 02:02:51AM -0600, Jan Beulich wrote:
> Non-debugging message text should be (and is in the cases here)
> distinguishable without also logging function names. Debugging message
> text, otoh, already includes file name and line number, so also
> logging function names is redun
On Wed, Aug 24, 2016 at 02:01:09AM -0600, Jan Beulich wrote:
> Non-debugging message text should be (and is here) distinguishable
> without also logging function names.
Reviewed-by: Konrad Rzeszutek Wilk
>
> Signed-off-by: Jan Beulich
>
> --- a/xen/arch/x86/mm/paging.c
> +++ b/xen/arch/x86/mm
On Wed, Aug 24, 2016 at 09:24:38AM -0600, Jan Beulich wrote:
> Program and section headers disagreed about the file offset at which
> the build ID note lives.
Gosh. That was an oversight.
>
> Reported-by: Sylvain Munaut
'whatever-company'? Really?
Huh. Imagine that.
> Signed-off-by: Jan Beuli
On 08/16/2016 06:25 AM, Shannon Zhao wrote:
> diff --git a/tools/libacpi/Makefile b/tools/libacpi/Makefile
> index d741ac5..7f50a33 100644
> --- a/tools/libacpi/Makefile
> +++ b/tools/libacpi/Makefile
> @@ -19,6 +19,7 @@ MK_DSDT = $(ACPI_BUILD_DIR)/mk_dsdt
>
> # Sources to be generated
> C_SRC
flight 100607 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/100607/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-libvirt-xsm 4 host-ping-check-native fail REGR. vs. 100602
test-armhf-armhf-x
On 08/16/2016 06:25 AM, Shannon Zhao wrote:
> diff --git a/xen/include/public/hvm/params.h b/xen/include/public/hvm/params.h
> index f7338a3..8a0327d 100644
> --- a/xen/include/public/hvm/params.h
> +++ b/xen/include/public/hvm/params.h
> @@ -30,6 +30,7 @@
> */
>
> #define HVM_PARAM_CALLBACK_I
flight 100608 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/100608/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-xl-qemuu-win7-amd64 16 guest-stop fail like 100589
test-amd64-amd64-xl-rtds
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Wednesday, August 24, 2016 3:54 PM
>
> Debugging message text already includes file name and line number, so
> also logging function names is redundant.
>
> Signed-off-by: Jan Beulich
>
Acked-by: Kevin Tian
__
> -Original Message-
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Wednesday, August 24, 2016 3:54 PM
> To: xen-devel
> Cc: Wu, Feng ; Tian, Kevin
> Subject: [PATCH] VT-d: drop pointless uses of __func__
>
> Debugging message text already includes file name and line number, so
On Wed, 24 Aug 2016 22:12:53 +0200
"Luis R. Rodriguez" wrote:
> On Wed, Aug 24, 2016 at 01:51:41PM +1000, Nicholas Piggin wrote:
> > On Tue, 23 Aug 2016 19:33:06 +0200
> > "Luis R. Rodriguez" wrote:
> >
> > > On Tue, Aug 23, 2016 at 11:26:33AM +1000, Nicholas Piggin wrote:
> > > > On Fri, 1
This patch is the xl/xc changes to support Intel L2 CAT
(Cache Allocation Technology).
The new level option is introduced to original CAT setting
command in order to set CBM for specified level CAT.
- 'xl psr-hwinfo' is updated to show both L3 CAT and L2 CAT
info.
- 'xl psr-cat-cbm-set' is updat
Add L2 CAT (Cache Allocation Technology) feature support in
hypervisor:
- Implement 'struct feat_ops' callback functions for L2 CAT
and initialize L2 CAT feature and add it into feature list.
- Add new sysctl to get L2 CAT information.
- Add new domctl to set/get L2 CAT CBM.
Signed-off-by: He Ch
Current psr.c is designed for supporting L3 CAT/CDP. It has many
limitations to add new feature. Considering to support more PSR
features, we need refactor PSR implementation to make it more
flexible and fulfill the principle, open for extension but closed
for modification.
The core of the refacto
Design document is below:
===
% Intel L2 Cache Allocation Technology (L2 CAT) Feature
% Revision 1.0
\clearpage
Hi all,
We plan to bring a new PSR (Platform Shared Resource) feature called
Intel L2 Cache Allocation Technology (L
flight 100610 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/100610/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
build-amd64-rumpuserxen 6 xen-buildfail like 100602
build-i386-rumpuserxen
On 22/08/16 19:25, David Vrabel wrote:
> On 04/08/16 16:16, David Vrabel wrote:
>> Currently libxencall using mlocked buffers for hypercall buffers.
>> This pages are subject to compaction and page migration. A userspace
>> process may see a hypercall fail with -EFAULT if a page backing a
>> hyperc
This run is configured for baseline tests only.
flight 67590 qemu-mainline real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/67590/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-xsm 11 guest-start
On Thu, Aug 25, 2016 at 12:06:33PM +1000, Nicholas Piggin wrote:
> On Wed, 24 Aug 2016 22:12:53 +0200
> "Luis R. Rodriguez" wrote:
> > But:
> >
> > git grep SECTION_TEXT works as expected immediately.
> >
> > I guess its a matter of perspective.
> >
> > > They are also
> > > the names you'll be
>>> On 25.08.16 at 03:08, wrote:
>> From: Jan Beulich [mailto:jbeul...@suse.com]
>> Subject: [PATCH] VT-d: drop pointless uses of __func__
>> --- a/xen/drivers/passthrough/vtd/iommu.c
>> +++ b/xen/drivers/passthrough/vtd/iommu.c
>> @@ -129,11 +129,11 @@ static int context_get_domain_id(struct
>>
>>> On 24.08.16 at 22:34, wrote:
> On Wed, Aug 24, 2016 at 02:02:51AM -0600, Jan Beulich wrote:
>> Non-debugging message text should be (and is in the cases here)
>> distinguishable without also logging function names. Debugging message
>> text, otoh, already includes file name and line number, so
On Thu, 25 Aug 2016 08:05:40 +0200
"Luis R. Rodriguez" wrote:
> On Thu, Aug 25, 2016 at 12:06:33PM +1000, Nicholas Piggin wrote:
> > On Wed, 24 Aug 2016 22:12:53 +0200
> > "Luis R. Rodriguez" wrote:
> > > But:
> > >
> > > git grep SECTION_TEXT works as expected immediately.
> > >
> > > I gue
Recent enough binutils (2.25 onwards) support --build-id also for
COFF/PE output, and hence we should use that in favor of the original
hack when possible.
This gets complicated by the linker requiring at least one COFF object
file to attach the .buildid section to. Hence the patch introduces a
bu
Section start symbols frequently obscure the actual symbol name living
at the start of the section. Eliminate them where they can be replaced
by linker resolved .startof.* symbols. (Section end symbols may have
the same undesirable effect, but they're less easy to eliminate, as
they'd need to be re
Non-debugging message text should be (and is in the cases here)
distinguishable without also logging function names. Additionally log
the PCI device coordinates for alloc_pdev() failure.
Signed-off-by: Jan Beulich
--- a/xen/drivers/passthrough/pci.c
+++ b/xen/drivers/passthrough/pci.c
@@ -379,8
Debugging message text already includes file name and line number, so
also logging function names is redundant.
Signed-off-by: Jan Beulich
--- a/xen/drivers/passthrough/vtd/intremap.c
+++ b/xen/drivers/passthrough/vtd/intremap.c
@@ -242,8 +242,8 @@ static int remap_entry_to_ioapic_rte(
if (
Non-debugging message text should be (and is here) distinguishable
without also logging function names.
Signed-off-by: Jan Beulich
--- a/xen/arch/x86/mm/paging.c
+++ b/xen/arch/x86/mm/paging.c
@@ -469,8 +469,9 @@ static int paging_log_dirty_op(struct do
peek = 0;
if ( unlikely(d-
Non-debugging message text should be (and is in the cases here)
distinguishable without also logging function names. Debugging message
text, otoh, already includes file name and line number, so also
logging function names is redundant. One relatively pointless debugging
message gets removed altoget
Non-debugging message text should be (and is in the cases here)
distinguishable without also logging function names.
Signed-off-by: Jan Beulich
--- a/xen/xsm/flask/hooks.c
+++ b/xen/xsm/flask/hooks.c
@@ -241,8 +241,8 @@ static int flask_evtchn_interdomain(stru
rc = security_transition_sid(s
flight 100603 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/100603/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt-xsm 12 migrate-support-checkfail never pass
test-amd64-i386-libvirt-xsm 12 migrate-s
flight 67588 distros-debian-squeeze real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/67588/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-amd64-squeeze-netboot-pygrub 9 debian-di-install fail like
67547
test-amd64-
>>> On 23.08.16 at 19:26, wrote:
> There is no need to extend the workaround to the faulted CPUID view, as
> Linux's dependence on the workaround is stricly via the emulated view.
>
> This causes a guest kernel faulted CPUID to observe architectural behaviour
> with respect to its CR4.OSXSAVE set
>>> On 23.08.16 at 19:26, wrote:
> A subsequent change needs to special-case OSXSAVE handling, which is per-vcpu
> rather than per-domain.
>
> No functional change.
>
> Signed-off-by: Andrew Cooper
Reviewed-by: Jan Beulich
___
Xen-devel mailing li
flight 100604 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/100604/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf d82d59edb0ec23e6ef708e04a5553ac32f1eb12e
baseline version:
ovmf 4962fcfa7d265824f01f7
>>> On 23.08.16 at 19:26, wrote:
> Contrary to c/s b2507fe7 "x86/domctl: Update PV domain cpumasks when setting
> cpuid policy", Intel CPUID masks are applied after fast forwarding hardware
> state, rather than before. (All behaviour in this regard appears completely
> undocumented by both Intel
Add grant table userspace device mappings for
FreeBSD (enables support for qdisk backend
on FreeBSD Dom0).
Signed-off-by: Akshay Jaggi
---
Changed since v1:
* fix coding style
* remove O_CLOEXEC
* remove SET_MAX_GRANTS ioctl
* update freebsd/gntdev.h to latest version
* replace alloca with
>>> On 24.08.16 at 04:22, wrote:
> --- a/xen/common/livepatch.c
> +++ b/xen/common/livepatch.c
> @@ -70,6 +70,9 @@ struct payload {
> unsigned int nsyms; /* Nr of entries in .strtab and
> symbols. */
> struct livepatch_build_id id;/* ELFNOTE_DESC(.note.gnu.build
>>> On 24.08.16 at 04:22, wrote:
> Livepatch expected at some point to be able to print the
> build-id during bootup, which it did not. The reason is
> that xen_build_init and livepatch_init are both __initcall
> type routines. This meant that when livepatch_init called
> xen_build_id, it would r
>>> On 24.08.16 at 04:22, wrote:
> --- a/xen/common/livepatch.c
> +++ b/xen/common/livepatch.c
> @@ -237,13 +237,34 @@ static const char *livepatch_symbols_lookup(unsigned
> long addr,
> static int resolve_old_address(struct livepatch_func *f,
> const struct livep
>>> On 24.08.16 at 04:22, wrote:
> The NOP functionality will NOP any of the code at
> the 'old_addr' or at 'name' if the 'new_addr' is zero.
> The purpose of this is to NOP out calls, such as:
>
> e8 <4-bytes-offset>
>
> (5 byte insn), or on ARM a 4 byte insn for branching.
> But on x86 we cou
>>> On 24.08.16 at 04:22, wrote:
> You could construct _most_ of the names of the functions
> by doing 'nm --defined' but unfortunatly you do not get the
> prefix that is added on in Xen . For example:
>
> $ cat xen-syms.symbols |grep do_domain_pause
> 0x82d080104920 t domain.c#do_domain_pau
On Tue, Aug 23, 2016 at 04:00:24PM -0400, Doug Goldstein wrote:
> On 8/18/16 10:13 AM, Wei Liu wrote:
>
> >
> > +if (info->device_model_version == LIBXL_DEVICE_MODEL_VERSION_QEMU_XEN)
> > {
> > +if (info->u.hvm.system_firmware) {
> > +bios_filename = info->u.hvm.system_f
Does anyone remember why the the vbd frontend drivers also claim the
SCSI disks, but the vbd backend in qemu has no unplug support for SCSI?
The current situation for qemu-xen and qemu-xen-traditional is that both
will create an emulated LSI controller with disk=[vdev=sda]. The
xenlinux and pvops
On Fri, Aug 12, 2016 at 06:32:34PM +0100, Lars Kurth wrote:
> In addition:
> - fixed a reference, which was incorrect
>
> Signed-off-by: Lars Kurth
Reviewed-by: Wei Liu
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-deve
On Fri, Aug 12, 2016 at 06:32:36PM +0100, Lars Kurth wrote:
> Blktap2 has some complexity, as some files do not have (c) headers
> and the directory did not have a COPYING file. At this stage, we
> have not verified the intention of (c) holders. We may do this in
> future, if the need arises.
>
>
>>> On 19.08.16 at 12:20, wrote:
> Changes in v3:
> * Fix boot options.
> * Fix CR4 & mmu_cr4_features operations.
> * Disable SMEP/SMAP for Dom0.
> * Commit message refinement.
Several of my comments on v3 did not get taken care of (neither in
code nor verbally). I'm not going to repeat them her
Hi,
Here's the readelf output (snipped) on a xen-4.7 build :
Section Headers:
[Nr] Name TypeAddr OffSize ES Flg Lk Inf Al
[ 0] NULL 00 00 00 0 0 0
[ 1] .text PROGBITS0010 80
On Fri, Aug 12, 2016 at 06:32:35PM +0100, Lars Kurth wrote:
> Added a COPYING file as a boilerplate to explain license oddities in
> this directory
>
> Added a vtpm/COPYING file which contains MIT licensed files only
>
> Added a vtpmmgr/README.source file which contains many BSD-3-Clause
> files
When remapping the page allocator's bitmap for the ballooning support
the calculation of the needed size is wrong. This doesn't really
matter today as nothing is allocated after that bitmap, but it should
be corrected nevertheless.
Signed-off-by: Juergen Gross
Reviewed-by: Samuel Thibault
---
b
In order to support HVMlite we need to get the ring page and event
channel from the hypervisor via hypercalls. Move the already existing
get_xenbus() function from arm specific coding to xenbus/xenbus.c and
provide a similar paravirtualized function.
Signed-off-by: Juergen Gross
Reviewed-by: Samu
Select what to print in arch_init() depending on the domain type.
Signed-off-by: Juergen Gross
Reviewed-by: Samuel Thibault
---
V2: add printing nr_modules as requested by Samuel Thibault
---
arch/x86/setup.c | 48 +---
1 file changed, 33 insertions(+
On HVMlite we have to look at the physical memory map to know which
memory frames are usable.
In order to make life easier we define a dummy memory map for other
domain types (pv and arm) which has just one entry with a maximum
memory size.
Signed-off-by: Juergen Gross
Reviewed-by: Samuel Thibau
Especially page table entry definitions are currently not usable from
assembler sources on x86 as the constants are defined with ULL suffix.
Change this by adding the suffix only when the header is included from
a C source.
Hide some C prototypes when in assembler environment.
Signed-off-by: Juer
Add a new config macro CONFIG_PARAVIRT which defaults to be defined on
x86. This is the first step for supporting a HVMlite Mini-OS.
Doing this via CONFIG_PARAVIRT instead of something like CONFIG_HVMLITE
was chosen as the arm port can then drop some dummy routines needed for
para-virtualization o
A HVMlite domain is always starting in 32 bit mode. Add the appropriate
boot code to arch/x86 for the non-paravirtualized case.
For this boot code to become active we need to suppress the pv related
elfnotes and add an appropriate elfnote for HVMlite.
As the HVMlite boot code is more or less the
dump_regs() will result in page fault in early boot as there is no
current thread pointer. Handle this case.
Signed-off-by: Juergen Gross
Reviewed-by: Samuel Thibault
---
arch/x86/traps.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/traps.c b/arch/x86/traps.c
ind
The start_info structure should be used only in case of CONFIG_PARAVIRT
defined. Remove it from being used in other places. Especially the
usage as parameter for applications linked to the kernel is no good
idea.
Signed-off-by: Juergen Gross
Reviewed-by: Samuel Thibault
---
arch/arm/setup.c
In HVMlite mode we need the virtual kernel area for mapping of the
console and xenbus ring pages as especially on 32 bit architecture
their pfns might be above the supported maximum memory size.
Add the page tables needed for doing the mapping.
Signed-off-by: Juergen Gross
Reviewed-by: Samuel Th
Support the HYPERVISOR_hvm_op() hypercall which is needed for HVMlite.
Add convenience functions hvm_get_parameter() and hvm_set_parameter().
Signed-off-by: Juergen Gross
Reviewed-by: Samuel Thibault
---
arch/arm/setup.c | 15 ---
hypervisor.c
Add a function map_frame_virt() to map a given frame and return its
virtual address.
On arm we just use the frame physical address, while on x86 we take a
page from the virtual kernel area. For this purpose make this area
available even in case of undefined CONFIG_BALLOON.
Signed-off-by: Juergen
Trap handling for HVMlite domains requires an initialized IDT.
Signed-off-by: Juergen Gross
Reviewed-by: Samuel Thibault
---
arch/x86/setup.c | 15 --
arch/x86/traps.c | 88 +++
arch/x86/x86_64.S | 4 +++
include/x86/os.h | 1 +
4
Trap handling in HVMlite domain is different from pv one.
Signed-off-by: Juergen Gross
Reviewed-by: Samuel Thibault
---
arch/x86/traps.c | 2 --
arch/x86/x86_32.S | 19 ++--
arch/x86/x86_64.S | 22 +-
include/x86/os.h | 67 +
In order to support HVMlite we need to get the ring page and event
channel from the hypervisor via hypercalls. Move the already existing
get_console() function from arm specific coding to
console/xencons_ring.c and provide a similar paravirtualized function.
Signed-off-by: Juergen Gross
Reviewed-
Use the latest Xen headers.
Signed-off-by: Juergen Gross
Reviewed-by: Samuel Thibault
---
include/xen/arch-x86/hvm/start_info.h | 98 +++
include/xen/elfnote.h | 12 -
2 files changed, 109 insertions(+), 1 deletion(-)
create mode 100644 inclu
The command line parameters are passed in start_info structure for pv,
but via hvm_start_info for HVMlite. Add a generic function to fill a
local cmdline variable with the command line string.
Signed-off-by: Juergen Gross
Reviewed-by: Samuel Thibault
---
arch/x86/setup.c | 20 ++
When running in HVMlite mode we need to setup the hypercall page by
ourself.
Signed-off-by: Juergen Gross
Reviewed-by: Samuel Thibault
---
V2: move wrmsr definitions as requested by Samuel Thibault
---
arch/x86/events.c | 4 ++--
arch/x86/setup.c | 26 ++
include/x86/o
This patch series adds HVMlite support for Mini-OS. Setting
CONFIG_PARAVIRT to "n" (default is "y") will build mini-os as a
HVMlite domain on x86. Both 32- and 64-bit builds are supported.
Tested with plain Mini-OS configuration to work in 32- and 64-bit
mode either paravirtualized or as HVM domai
All handling related to p2m is needed for paravirtualized environment
only. So put all functions operating on p2m list in #ifdef
CONFIG_PARAVIRT sections. Add a paravirt.h header defining dummy
functions for non-paravirtualized environments. Instead of using
references to start_info use dedicated v
Add a service function to map the shared info page on a
non-paravirtualized system. The code is already existing on ARM side,
just move it to hypervisor.c.
Signed-off-by: Juergen Gross
Reviewed-by: Samuel Thibault
---
arch/arm/arm32.S | 4 ++--
arch/arm/setup.c | 11 +--
arch/x
Instead of calling HYPERVISOR_sched_op(SCHEDOP_block, 0) we need to use
the "hlt" instruction with interrupts enabled to switch to idle when
running as HVMlite domain.
This requires to setup a new timer in the timer handler as there is no
guarantee the original timer event we are waiting for won't
For support of HVMlite don't use mmu_update hypercalls, but write the
page table entries directly.
Signed-off-by: Juergen Gross
Reviewed-by: Samuel Thibault
---
arch/x86/mm.c | 147 +-
arch/x86/traps.c | 10
include/x86/arch_mm.
Juergen Gross, on Wed 24 Aug 2016 12:11:27 +0200, wrote:
> A HVMlite domain is always starting in 32 bit mode. Add the appropriate
> boot code to arch/x86 for the non-paravirtualized case.
>
> For this boot code to become active we need to suppress the pv related
> elfnotes and add an appropriate
>>> On 23.08.16 at 03:54, wrote:
> AVX512 is an extention of AVX2. Its spec can be found at:
> https://software.intel.com/sites/default/files/managed/b4/3a/319433-024.pdf
> This patch detects AVX512 features by CPUID.
>
> Signed-off-by: Luwei Kang
Reviewed-by: Jan Beulich
But I'd specificall
On Wed, Aug 24, 2016 at 11:10:02AM +0100, Wei Liu wrote:
> On Fri, Aug 12, 2016 at 06:32:35PM +0100, Lars Kurth wrote:
> > Added a COPYING file as a boilerplate to explain license oddities in
> > this directory
> >
> > Added a vtpm/COPYING file which contains MIT licensed files only
> >
> > Added
>>> On 24.08.16 at 12:07, wrote:
> Hi,
>
> Here's the readelf output (snipped) on a xen-4.7 build :
>
> Section Headers:
> [Nr] Name TypeAddr OffSize ES Flg Lk
> Inf Al
> [ 0] NULL 00 00 00 0
> 0 0
>
On Wed, Aug 24, 2016 at 12:11:22PM +0200, Juergen Gross wrote:
> This patch series adds HVMlite support for Mini-OS. Setting
> CONFIG_PARAVIRT to "n" (default is "y") will build mini-os as a
> HVMlite domain on x86. Both 32- and 64-bit builds are supported.
>
> Tested with plain Mini-OS configurat
flight 100605 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/100605/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xen 94d3b9990bf73459919fb5b234d088d1ac41c9da
baseline version:
xen 2a99
On Fri, Aug 19, 2016 at 08:45:49PM +0430, Cendrin Sa wrote:
> Hi again,
> So save/restore has a bug or not? I still have problem with it when i use
> LVM.
>
I think we need more logs.
Which task hung? Can you provide kernel backtrace?
Wei.
___
Xen-de
flight 100602 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/100602/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-armhf-armhf-xl-arndale 6 xen-boot fail in 100592 pass in 100602
test-armhf-armhf-xl 15
On Fri, Aug 19, 2016 at 08:45:49PM +0430, Cendrin Sa wrote:
> Hi again,
> So save/restore has a bug or not? I still have problem with it when i use
> LVM.
Which kernel version are you using on the Dom0?
Roger.
___
Xen-devel mailing list
Xen-devel@lists
On Mon, Aug 08, 2016 at 07:31:28PM +0200, Juergen Gross wrote:
> On 08/08/16 16:45, Ian Jackson wrote:
> > Juergen Gross writes ("[PATCH 0/3] tools: support autoballooning of
> > xenstore domain"):
> >> Support xenstore domain autoballooning by:
> >> - adding --maxmem parameter to init-xenstore-do
This run is configured for baseline tests only.
flight 67589 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/67589/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf d82d59edb0ec23e6ef708e04a5553ac32f1eb12e
baseline v
During test of HVMlite Mini-OS I found that the memory size obtained
via HYPERVISOR_memory_op(XENMEM_current_reservation) was higher than
expected: for a 16MB domain the number of pages was 8 pages larger than
I thought it should be. This seems to include the p2m map allocated by
the toolstack.
Th
Wei Liu writes ("[PATCH 0/2] Fix issue with {OVMF,SEABIOS}_PATH"):
> They shouldn't be available when the respective BIOS is disabled at build
> time.
>
> This should fix the issus that causes xtf fail to launch hvm guests.
Both
Acked-by: Ian Jackson
Thanks,
Ian.
On Wed, Aug 24, 2016 at 12:38:06PM +0100, Ian Jackson wrote:
> Wei Liu writes ("[PATCH 0/2] Fix issue with {OVMF,SEABIOS}_PATH"):
> > They shouldn't be available when the respective BIOS is disabled at build
> > time.
> >
> > This should fix the issus that causes xtf fail to launch hvm guests.
>
On Wed, Aug 17, 2016 at 12:17:12AM +0200, Sergej Proskurin wrote:
> From: Tamas K Lengyel
>
> Currently setting altp2mhvm=1 in the domain configuration allows access to the
> altp2m interface for both in-guest and external privileged tools. This poses
> a problem for use-cases where only external
On Wed, Aug 17, 2016 at 12:17:14AM +0200, Sergej Proskurin wrote:
> This commit extends xen-access by a simple test of the functionality
> provided by "xc_altp2m_change_gfn". The idea is to dynamically remap a
> trapping gfn to another mfn, which holds the same content as the
> original mfn. On suc
This patch proposes relying on host TSC synchronization and
passthrough to the guest, when running on a TSC-safe platform. On
time_calibration we retrieve the platform time in ns and the counter
read by the clocksource that was used to compute system time. We
introduce a new rendezous function whic
And use to initialize platform time solely for clocksource=tsc,
as opposed to initializing platform overflow timer, which would
only fire in ~180 years (on 2.2 Ghz Broadwell processor).
Signed-off-by: Joao Martins
---
Cc: Jan Beulich
Cc: Andrew Cooper
Changes since v2:
- Remove pointless inti
Recent x86/time changes improved a lot of the monotonicity in xen timekeeping,
making it much harder to observe time going backwards. Although platform timer
can't be expected to be perfectly in sync with TSC and so get_s_time won't be
guaranteed to always return monotonically increasing values ac
To fetch the last read from the clocksource which was used to
calculate system_time. In the case of clocksource=tsc we will
use it to set tsc_timestamp.
Signed-off-by: Joao Martins
---
Cc: Jan Beulich
Cc: Andrew Cooper
Changes since v2:
- s/plt_stamp_counter/plt_counter/g
- Move conditional
And accomodate platform time source initialization in
try_platform_time(). This is a preparatory patch for deferring
TSC clocksource initialization to the stage where all CPUS are
up (verify_tsc_reliability init call).
Signed-off-by: Joao Martins
Reviewed-by: Konrad Rzeszutek Wilk
---
Cc: Jan Be
Add TSC as another clocksource that can be used, plus
a mention to the maxcpus parameter and that it requires
being explicitly set.
Signed-off-by: Joao Martins
---
Cc: Andrew Cooper
Cc: Jan Beulich
New in v3.
---
docs/misc/xen-command-line.markdown | 6 +-
1 file changed, 5 insertions(+),
Hey!
This is v3 on the pvclock TSC stable bit series.
Complete changelog on individual patches but overall is addressing
Jan's comments, plus some other changes regarding the recent monotonicity
improvements on x86/time.
Series is divided as follows:
R * Patch 1: Small refactor around ini
Hi Jan,
> Indeed, patch in the works. But why did you not provide a patch
> yourself, considering that you've done all the diagnosis?
I read the code of that tool this morning and couldn't really
understand how "offset" was computed.
I was seeing :
offset = in64_phdr.p_offset;
then a bit late
On 24/08/2016 06:10, "Wei Liu" wrote:
>
>> diff --git a/stubdom/vtpmmgr/README.source
>>b/stubdom/vtpmmgr/README.source
>> new file mode 100644
>> index 000..1b45997
>> --- /dev/null
>> +++ b/stubdom/vtpmmgr/README.source
>> @@ -0,0 +1,23 @@
>> +About
>> +=
>> +This documents the upstre
[Missed CC-ing the maintainers in the cover letter, my apologies]
On 08/24/2016 01:43 PM, Joao Martins wrote:
> Hey!
>
> This is v3 on the pvclock TSC stable bit series.
>
> Complete changelog on individual patches but overall is addressing
> Jan's comments, plus some other changes regarding the
On Tue, Aug 16, 2016 at 06:24:58PM +0800, Shannon Zhao wrote:
> From: Shannon Zhao
>
> Since the existing configuration option "u.hvm.acpi" is x86 specific and
> we want to reuse it on ARM as well, add a unified option "acpi" for
> x86 and ARM, and for ARM it's disabled by default.
>
> Signed-of
On Tue, Aug 16, 2016 at 06:25:02PM +0800, Shannon Zhao wrote:
> From: Shannon Zhao
>
> Construct ACPI RSDP table and add a helper to calculate the ACPI table
> checksum.
>
> Signed-off-by: Shannon Zhao
> ---
> tools/libxl/libxl_arm_acpi.c | 38 ++
> 1 file c
1 - 100 of 120 matches
Mail list logo
