This run is configured for baseline tests only.
flight 75045 ovmf real [real]
http://osstest.xensource.com/osstest/logs/75045/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-i386-xl-qemuu-ovmf-amd64 10 debian-hvm-install fail like 75044
test
flight 125755 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/125755/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 526dd0245bf0db6a01c21943201a4572747bca7f
baseline version:
ovmf dd4cae4d82c7477273f3d
On 8/2/18 3:22 PM, Kees Cook wrote:
> On Thu, Aug 2, 2018 at 12:22 PM, Srivatsa S. Bhat
> wrote:
>> On 7/26/18 4:09 PM, Kees Cook wrote:
>>> On Tue, Jul 24, 2018 at 3:02 PM, Jiri Kosina wrote:
On Tue, 24 Jul 2018, Srivatsa S. Bhat wrote:
> However, if you are proposing that you'd li
On Fri, 3 Aug 2018, Jan Beulich wrote:
> >>> On 02.08.18 at 22:57, wrote:
> > On Thu, 2 Aug 2018, Jan Beulich wrote:
> >> >> > +/*
> >> >> > + * This action also requires that @current targets @d, but it has
> >> >> > already been
> >> >> > + * checked somewhere higher in the call stack.
> >> >>
On 08/03/2018 08:22 PM, Paul Durrant wrote:
> The name 'need_iommu' is a little confusing as it suggests a domain needs
> to use the IOMMU but something might not be set up yet, when in fact it
> doesn't become true until IOMMU mappings for the domain have been created.
>
> Two different meanings
On Fri, 3 Aug 2018, Artem Mygaiev wrote:
> > Unfortunately, PV OpenGL is not available upstream at the moment. It was not
> > clear whether the backend and frontend would ever be upstreamed and when.
> >
> > However, the work looks quite similar to virgil
> > (https://virgil3d.github.io/). It is G
The name 'need_iommu' is a little confusing as it suggests a domain needs
to use the IOMMU but something might not be set up yet, when in fact it
doesn't become true until IOMMU mappings for the domain have been created.
Two different meanings are also inferred from it in various places in the
cod
The name 'iommu_use_hap_pt' suggests that that P2M table is in use as the
domain's IOMMU pagetable which, prior to this patch, is not strictly true
since the macro did not test whether the domain actually has IOMMU
mappings.
Signed-off-by: Paul Durrant
---
Cc: Jun Nakajima
Cc: Kevin Tian
Cc: Ge
This patch adds iommu_ops to add (map) or remove (unmap) frames in the
domain's IOMMU mappings, and an iommu_op to synchronize (flush) those
manipulations with the hardware.
Mappings added by the map operation are tracked and only those mappings
may be removed by a subsequent unmap operation. Fram
...for some uses of get_page_from_gfn().
There are many occurences of the following pattern in the code:
q = ? P2M_ALLOC : P2M_UNSHARE;
page = get_page_from_gfn(d, gfn, &p2mt, q);
if ( p2m_is_paging(p2mt) )
{
if ( page )
put_page(page);
p2m_mem_pagin
This patch adds an iommu_op which checks whether it is possible or
safe for a domain to modify its own IOMMU mappings and, if so, creates
a rangeset to track modifications.
NOTE: The actual map and unmap operations are introduced by subsequent
patches.
Signed-off-by: Paul Durrant
---
Cc: J
This patch allows a domain to add or remove foreign frames from its
IOMMU mappings by grant reference as well as GFN. This is necessary,
for example, to support a PV network backend that needs to construct a
packet buffer that can be directly accessed by a NIC.
Signed-off-by: Paul Durrant
---
Cc:
On Thu, Aug 02, 2018 at 01:17:37PM +0200, Roger Pau Monné wrote:
> On Fri, Jul 27, 2018 at 03:06:04PM +0100, Anthony PERARD wrote:
> > This will handles messages received, and calls callbacks associated with
> ^ handle
>
> I'm not sure I understand what's 'This' in the context. Would b
The idea of a paravirtual IOMMU interface was last discussed on xen-devel
several years ago and narrowed down on a draft specification [1].
There was also an RFC patch series posted with an implementation, however
this was never followed through.
In this patch series I have tried to simplify the i
This patch modifies the declaration of the entry points to the IOMMU
sub-system to use bfn_t and mfn_t in place of unsigned long. A subsequent
patch will similarly modify the methods in the iommu_ops structure.
Signed-off-by: Paul Durrant
Reviewed-by: Wei Liu
---
Cc: Jan Beulich
Cc: Andrew Coop
As noted in [1] the tri-state nature of need_iommu after commit 3e06b989 is
confusing.
Because arch_iommu_populate_page_table() removes pages from the page list
as it maps them it is actually safe to re-invoke multiple times without
the need for any specific indication it has been called before, s
This patch modifies the methods in struct iommu_ops to use type-safe BFN
and MFN. This follows on from the prior patch that modified the functions
exported in xen/iommu.h.
Signed-off-by: Paul Durrant
Reviewed-by: Wei Liu
---
Cc: Suravee Suthikulpanit
Cc: Jan Beulich
Cc: Kevin Tian
Cc: Andrew
This patch adds a new method to the VT-d IOMMU implementation to find the
MFN currently mapped by the specified BFN along with a wrapper function in
generic IOMMU code to call the implementation if it exists.
This functionality will be used by a subsequent patch.
Signed-off-by: Paul Durrant
Revi
This patch introduces the boilerplate for a new hypercall to allow a
domain to control IOMMU mappings for its own pages.
Whilst there is duplication of code between the native and compat entry
points which appears ripe for some form of combination, I think it is
better to maintain the separation as
Turn iommu_map/unmap_page() into straightforward wrappers that check the
existence of the relevant iommu_op and call through to it. This makes them
usable by PV IOMMU code to be delivered in future patches.
Leave the decision on whether to invoke domain_crash() up to the caller.
This has the added
Ranges that should be considered reserved in the IOMMU are not necessarily
limited to RMRRs. If iommu_inclusive_mapping is set then any frame number
falling within an E820 reserved region should also be considered as
reserved in the IOMMU.
This patch adds a rangeset to the domain_iommu structure th
...meaning 'bus frame number' i.e. a frame number mapped in the IOMMU
rather than the MMU.
This patch is a largely cosmetic change that substitutes the terms 'gfn'
and 'gaddr' for 'bfn' and 'baddr' in all the places where the frame number
or address relate to the IOMMU rather than the MMU.
The pa
This patch adds an iommu_op to allow the domain IOMMU reserved ranges to be
queried by the guest.
NOTE: The number of reserved ranges is determined by system firmware, in
conjunction with Xen command line options, and is expected to be
small. Thus, to avoid over-complicating the code,
On Thu, Aug 02, 2018 at 01:02:13PM +0200, Roger Pau Monné wrote:
> On Fri, Jul 27, 2018 at 03:06:02PM +0100, Anthony PERARD wrote:
> > The libxl__ev_qmp_* will now send the command to QEMU when the socket is
> > ready for writes.
> >
> > Signed-off-by: Anthony PERARD
>
> Reviewed-by: Roger Pau M
On Thu, Aug 02, 2018 at 12:41:26PM +0200, Roger Pau Monné wrote:
> On Fri, Jul 27, 2018 at 03:06:01PM +0100, Anthony PERARD wrote:
> > The actual sent will be done in a separate patch.
> >
> > Signed-off-by: Anthony PERARD
> > ---
> > tools/libxl/libxl_internal.h | 4
> > tools/libxl/libxl
On Thu, Aug 02, 2018 at 12:34:31PM +0200, Roger Pau Monné wrote:
> On Fri, Jul 27, 2018 at 03:06:00PM +0100, Anthony PERARD wrote:
> > To be able to re-use qmp_prepare_qmp_cmd with libxl__ev_qmp.
> >
> > Also, add the QMP end of command '\r\n' into the generated string.
> >
> > Signed-off-by: Ant
On Thu, Aug 02, 2018 at 12:25:53PM +0200, Roger Pau Monné wrote:
> On Fri, Jul 27, 2018 at 03:05:59PM +0100, Anthony PERARD wrote:
> > +/* workaround strstr limitation */
> > +ev->rx_buf[ev->buf_used] = '\0';
>
> Why not use strnstr to limit the size of the rx_buf that's searched? I
> thin
On Fri, Aug 03, 2018 at 03:45:39PM +0100, Anthony PERARD wrote:
> On Fri, Aug 03, 2018 at 03:55:48PM +0200, Roger Pau Monné wrote:
> > On Fri, Aug 03, 2018 at 12:18:02PM +0100, Anthony PERARD wrote:
> > > On Thu, Aug 02, 2018 at 11:01:43AM +0200, Roger Pau Monné wrote:
> > > > On Fri, Jul 27, 2018
On 03/08/18 16:23, Jan Beulich wrote:
> Both are entirely unused (to be fair, reserve_bootmem() has a use inside
> an "#if 0" section in x86's mpparse.c, but if we were to re-enable that
> code, it would need doing differently anyway).
>
> Signed-off-by: Jan Beulich
Acked-by: Andrew Cooper
Can
On Fri, Aug 03, 2018 at 03:32:09PM +0100, Anthony PERARD wrote:
> On Thu, Aug 02, 2018 at 11:56:11AM +0200, Roger Pau Monné wrote:
> > On Fri, Jul 27, 2018 at 03:05:56PM +0100, Anthony PERARD wrote:
> > > +/* The -1 is because there is always space for a NUL character */
> > > +r =
On Fri, Aug 03, 2018 at 09:23:06AM -0600, Jan Beulich wrote:
> Both are entirely unused (to be fair, reserve_bootmem() has a use inside
> an "#if 0" section in x86's mpparse.c, but if we were to re-enable that
> code, it would need doing differently anyway).
>
> Signed-off-by: Jan Beulich
Review
Both are entirely unused (to be fair, reserve_bootmem() has a use inside
an "#if 0" section in x86's mpparse.c, but if we were to re-enable that
code, it would need doing differently anyway).
Signed-off-by: Jan Beulich
--- a/xen/include/asm-x86/acpi.h
+++ b/xen/include/asm-x86/acpi.h
@@ -98,9 +9
On Fri, Aug 03, 2018 at 09:46:46AM -0500, Doug Goldstein wrote:
> Standardized all the environment variable names that the containerize
> script uses to start with CONTAINER_
>
> Signed-off-by: Doug Goldstein
Reviewed-by: Wei Liu
___
Xen-devel mailin
This is more dead code.
Signed-off-by: Doug Goldstein
Reviewed-by: Wei Liu
---
automation/scripts/containerize | 5 -
1 file changed, 5 deletions(-)
diff --git a/automation/scripts/containerize b/automation/scripts/containerize
index 7f0eb0a..7bdfc21 100755
--- a/automation/scripts/contain
friendly for folks to use to locally do build tests under different
distros.
change from v1:
- first patch switch to -z as it makes more sense
Doug Goldstein (4):
automation: standardize containerize env names
automation: drop container name from containerize
automation: remove dead code fr
This was something that existed for some scripting support for a totally
unrelated project and when I copied this script I failed to remove it so
this removes it. Build containers for Xen are best as ephemeral
environments and should just utilizes Docker's default container naming
behavior.
Signed
Standardized all the environment variable names that the containerize
script uses to start with CONTAINER_
Signed-off-by: Doug Goldstein
---
automation/build/README.md | 10 +-
automation/scripts/containerize | 10 --
2 files changed, 9 insertions(+), 11 deletions(-)
diff -
By default the container runs as the root user and since the source tree
is bind mounted into the container, any file is created and owned by the
root user which harms ergonomics when working outside of the container
environment. This maps the root user within the container to the uid of
the user o
On Fri, Aug 03, 2018 at 03:55:48PM +0200, Roger Pau Monné wrote:
> On Fri, Aug 03, 2018 at 12:18:02PM +0100, Anthony PERARD wrote:
> > On Thu, Aug 02, 2018 at 11:01:43AM +0200, Roger Pau Monné wrote:
> > > On Fri, Jul 27, 2018 at 03:05:54PM +0100, Anthony PERARD wrote:
> > > > +/*
> > > > + * This
On Thu, Aug 02, 2018 at 11:56:11AM +0200, Roger Pau Monné wrote:
> On Fri, Jul 27, 2018 at 03:05:56PM +0100, Anthony PERARD wrote:
> > +/* The -1 is because there is always space for a NUL character */
> > +r = read(fd, ev->rx_buf + ev->buf_used,
> > + ev->buf_size -
On Fri, Aug 03, 2018 at 02:54:20PM +0100, Anthony PERARD wrote:
> On Thu, Aug 02, 2018 at 11:35:53AM +0200, Roger Pau Monné wrote:
> > On Fri, Jul 27, 2018 at 03:05:55PM +0100, Anthony PERARD wrote:
> > > +typedef enum {
> > > +qmp_state_disconnected = 1,
> > > +qmp_state_connecting,
> > >
On Fri, Aug 03, 2018 at 12:18:02PM +0100, Anthony PERARD wrote:
> On Thu, Aug 02, 2018 at 11:01:43AM +0200, Roger Pau Monné wrote:
> > On Fri, Jul 27, 2018 at 03:05:54PM +0100, Anthony PERARD wrote:
> > > +/*
> > > + * This facility allows a command to be sent to QEMU, and the response
> > > to be
This is used to save data from a single instance.
Signed-off-by: Alexandru Isaila
---
xen/arch/x86/hvm/vlapic.c | 27 +++
1 file changed, 19 insertions(+), 8 deletions(-)
diff --git a/xen/arch/x86/hvm/vlapic.c b/xen/arch/x86/hvm/vlapic.c
index 0795161..d35810e 100644
---
On Thu, Aug 02, 2018 at 11:35:53AM +0200, Roger Pau Monné wrote:
> On Fri, Jul 27, 2018 at 03:05:55PM +0100, Anthony PERARD wrote:
> > +typedef enum {
> > +qmp_state_disconnected = 1,
> > +qmp_state_connecting,
> > +qmp_state_greeting,
> > +qmp_state_capability_negociation,
> > +
This is used to save data from a single instance.
Signed-off-by: Alexandru Isaila
---
Changes since V13:
- Moved tsc_adjust to the initializer.
---
xen/arch/x86/hvm/hvm.c | 13 ++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git a/xen/arch/x86/hvm/hvm.c b/xen/arch
This patch removes the redundant save functions and renames the
save_one* to save. It then changes the domain param to vcpu in the
save funcs.
Signed-off-by: Alexandru Isaila
---
Changes since V14:
- Change vcpu to v
- Remove extra space
- Rename save_one handler to save
Signed-off-by: Alexandru Isaila
---
Changes since V14:
- Change handler name from hvm_save_one_handler to
hvm_save_vcpu_handler.
---
xen/arch/x86/cpu/mcheck/vmce.c | 1 +
xen/arch/x86/hvm/hpet.c| 2 +-
xen/arch/x86/hvm/hvm.c | 6 +-
xen/arch/x86/hvm/i8254.c
This is used to save data from a single instance.
Signed-off-by: Alexandru Isaila
Reviewed-by: Paul Durrant
---
Changes since V14:
- Remove err init
- Add blank line ahead of return.
---
xen/arch/x86/hvm/hvm.c | 106 +++--
1 file chan
This is used to save data from a single instance.
Signed-off-by: Alexandru Isaila
---
Changes since V11:
- Removed the memset and added init with {}.
---
xen/arch/x86/cpu/mcheck/vmce.c | 21 +
1 file changed, 13 insertions(+), 8 deletions(-)
diff --git a/xen/arch/x8
Hi all,
This patch series addresses the ideea of saving data from a single vcpu
instance.
First it starts by adding *save_one functions, then it introduces a handler for
the
new save_one* funcs and makes use of it in the hvm_save and hvm_save_one funcs.
The final patches are used for clean up an
This is used to save data from a single instance.
Signed-off-by: Alexandru Isaila
---
Changes since V14:
- Remove err init
- Add blank line ahead of return
- Move xsave_enabled() check to the save_one func.
---
xen/arch/x86/hvm/hvm.c | 47 +---
This is used to save data from a single instance.
Signed-off-by: Alexandru Isaila
---
Changes since v14:
- Fix style violations
- Use structure fields over cast
- Use memcpy for fixed_ranges.
Note: This patch is based on Roger Pau Monne's series[1]
---
xen/arch/x86/hvm/
This patch is aimed on using the new save_one fuctions in the hvm_save
Signed-off-by: Alexandru Isaila
---
Changes since V14:
- Removed the modification from the hvm_save_one
- Removed vcpu init
- Declared rc as int
- Add vcpu id to the log print.
---
xen/arch/x8
This is used to save data from a single instance.
Signed-off-by: Alexandru Isaila
---
xen/arch/x86/hvm/vlapic.c | 22 ++
1 file changed, 14 insertions(+), 8 deletions(-)
diff --git a/xen/arch/x86/hvm/vlapic.c b/xen/arch/x86/hvm/vlapic.c
index 1b9f00a..0795161 100644
--- a/xe
This patch drops the use of save functions in hvm_save.
Signed-off-by: Alexandru Isaila
---
xen/arch/x86/hvm/save.c | 25 -
1 file changed, 4 insertions(+), 21 deletions(-)
diff --git a/xen/arch/x86/hvm/save.c b/xen/arch/x86/hvm/save.c
index 61565fe..363695c 100644
--- a
This is used to save data from a single instance.
Signed-off-by: Alexandru Isaila
---
Changes since V14:
- Move all free fields to the initializer
- Add blank line to before the return
- Move v->pause_flags check to the save_one function.
---
xen/arch/x86/hvm/hvm.c | 219
This patch is focused on moving changing hvm_save_one() to save one
typecode from one vcpu and now that the save functions get data from a
single vcpu we can pause the specific vcpu instead of the domain.
Signed-off-by: Alexandru Isaila
---
xen/arch/x86/domctl.c | 4 ++--
xen/arch/x86/hvm/sav
This is used to save data from a single instance.
Signed-off-by: Alexandru Isaila
Reviewed-by: Paul Durrant
---
Changes since V14:
- Moved all the operations in the initializer.
---
xen/arch/x86/hvm/viridian.c | 30 +++---
1 file changed, 19 insertions(+), 11 de
On 03/08/18 14:20, Paul Durrant wrote:
> Because qemu-trad is using the legacy HVM param mechanism of hooking into
> Xen, it means that Xen has to maintain the notion of a 'default' IOREQ
> server which is where all I/O goes if no other device model claims it.
> Maintaining this code in Xen has a c
Because qemu-trad is using the legacy HVM param mechanism of hooking into
Xen, it means that Xen has to maintain the notion of a 'default' IOREQ
server which is where all I/O goes if no other device model claims it.
Maintaining this code in Xen has a cost and it would be good if the project
no long
flight 125754 freebsd-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/125754/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-freebsd 7 freebsd-buildfail REGR. vs. 125317
Tests which did
This run is configured for baseline tests only.
flight 75044 ovmf real [real]
http://osstest.xensource.com/osstest/logs/75044/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-i386-xl-qemuu-ovmf-amd64 10 debian-hvm-install fail like 75043
test
On Thu, Aug 02, 2018 at 11:01:43AM +0200, Roger Pau Monné wrote:
> On Fri, Jul 27, 2018 at 03:05:54PM +0100, Anthony PERARD wrote:
> > All the functions will be implemented in later patches.
> >
> > This patch includes the API that libxl can use to send QMP commands to
> > QEMU.
> >
> > Signed-of
On Fri, Aug 03, 2018 at 10:54:19AM +0100, Tim Deegan wrote:
> Hi,
>
> Apologies for the delay. Several of my other hats were on fire.
>
> > > I suspect the address, from which offset is derived, is bounded. But I
> > > haven't found the spec for KD.
> >
> > I don’t think there is one.
>
> Inde
On Thu, Aug 02, 2018 at 07:58:48AM +, Tian, Kevin wrote:
> > +void __hwdom_init arch_iommu_hwdom_init(struct domain *d)
> > +{
> > +unsigned long i, top, max_pfn;
> > +
> > +BUG_ON(!is_hardware_domain(d));
> > +
> > +/* Set the default value of inclusive depending on the hardware. *
Hi Julien
On 03.08.18 12:37, Julien Grall wrote:
On 08/02/2018 04:26 PM, Artem Mygaiev wrote:
Hello Julien
Hi Artem,
Thank you for the feedback!
On 02.08.18 12:56, Julien Grall wrote:
Hi,
Sorry for the late posting. The notes were taken by Stefano
Stabellini. Thank you.
This has some c
Hi,
Apologies for the delay. Several of my other hats were on fire.
> > I suspect the address, from which offset is derived, is bounded. But I
> > haven't found the spec for KD.
>
> I don’t think there is one.
Indeed not. The official way to extend windbg &c is to write a plugin
that runs on
flight 125752 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/125752/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf dd4cae4d82c7477273f3da455084844db5cca0c0
baseline version:
ovmf 1d802e234e813a6726f4c
On 08/02/2018 04:26 PM, Artem Mygaiev wrote:
Hello Julien
Hi Artem,
Thank you for the feedback!
On 02.08.18 12:56, Julien Grall wrote:
Hi,
Sorry for the late posting. The notes were taken by Stefano
Stabellini. Thank you.
This has some clarifications requested from EPAM regarding PowerV
> -Original Message-
[snip]
> > The problem then is what does, say, reserved + no-inclusive mean? I guess
> we could have a flag for each non ram E820 range type?
>
> reserved + no-inclusive would make sense for a PV Dom0 running on
> Intel hardware in order to map only the reserved region
On Fri, Aug 03, 2018 at 10:14:49AM +0100, Paul Durrant wrote:
> > -Original Message-
> > From: Roger Pau Monne
> > Sent: 03 August 2018 10:09
> > To: Paul Durrant
> > Cc: Jan Beulich ; Kevin Tian ;
> > Stefano Stabellini ; Wei Liu ;
> > George Dunlap ; Andrew Cooper
> > ; Ian Jackson ; Tim
On 03/08/2018 10:27, Alexandru Isaila wrote:
> This initializer is flawed and only sets .name of array entry 0
> to a non-NULL string.
>
> Signed-off-by: Alexandru Isaila
> Suggested-by: Jan Beulich
Acked-by: Andrew Cooper
___
Xen-devel mailing list
This initializer is flawed and only sets .name of array entry 0
to a non-NULL string.
Signed-off-by: Alexandru Isaila
Suggested-by: Jan Beulich
---
xen/arch/x86/hvm/save.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/xen/arch/x86/hvm/save.c b/xen/arch/x86/hvm/save.c
index
This run is configured for baseline tests only.
flight 75043 ovmf real [real]
http://osstest.xensource.com/osstest/logs/75043/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-i386-xl-qemuu-ovmf-amd64 10 debian-hvm-install fail like 75041
test
> -Original Message-
> From: Roger Pau Monne
> Sent: 03 August 2018 10:09
> To: Paul Durrant
> Cc: Jan Beulich ; Kevin Tian ;
> Stefano Stabellini ; Wei Liu ;
> George Dunlap ; Andrew Cooper
> ; Ian Jackson ; Tim
> (Xen.org) ; Julien Grall ; Suravee
> Suthikulpanit ; xen-devel de...@lists
Hi Stefano,
On 08/01/2018 11:25 PM, Stefano Stabellini wrote:
On Wed, 1 Aug 2018, Julien Grall wrote:
Hi,
On 31/07/18 19:23, Stefano Stabellini wrote:
Shared memory regions need to be advertised to the guest. Fortunately, a
device tree binding for special memory regions already exist:
reserve
flight 75042 distros-debian-jessie real [real]
http://osstest.xensource.com/osstest/logs/75042/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-armhf-jessie-netboot-pygrub 10 debian-di-install fail like
75015
baseline version:
flight
Hi Roger,
On 08/01/2018 12:03 PM, Roger Pau Monne wrote:
Introduce a new dom0-iommu=inclusive generic option that supersedes
iommu_inclusive_mapping. The prevcious behaviour is preserved and the
option should only be enabled by default on Intel hardware.
No functional change intended.
Signed-o
On Fri, Aug 03, 2018 at 10:05:19AM +0100, Paul Durrant wrote:
> > -Original Message-
> > From: Roger Pau Monne
> > Sent: 03 August 2018 09:52
> > To: Paul Durrant
> > Cc: Jan Beulich ; Kevin Tian ;
> > Stefano Stabellini ; Wei Liu ;
> > George Dunlap ; Andrew Cooper
> > ; Ian Jackson ; Tim
> -Original Message-
> From: Roger Pau Monne
> Sent: 03 August 2018 09:52
> To: Paul Durrant
> Cc: Jan Beulich ; Kevin Tian ;
> Stefano Stabellini ; Wei Liu ;
> George Dunlap ; Andrew Cooper
> ; Ian Jackson ; Tim
> (Xen.org) ; Julien Grall ; Suravee
> Suthikulpanit ; xen-devel de...@lists
On Fri, Aug 03, 2018 at 09:35:58AM +0100, Paul Durrant wrote:
> > -Original Message-
> > From: Xen-devel [mailto:xen-devel-boun...@lists.xenproject.org] On Behalf
> > Of Roger Pau Monné
> > Sent: 03 August 2018 09:14
> > To: Jan Beulich
> > Cc: Kevin Tian ; Stefano Stabellini
> > ; Wei Liu
> -Original Message-
> From: Xen-devel [mailto:xen-devel-boun...@lists.xenproject.org] On Behalf
> Of Roger Pau Monné
> Sent: 03 August 2018 09:14
> To: Jan Beulich
> Cc: Kevin Tian ; Stefano Stabellini
> ; Wei Liu ; George Dunlap
> ; Andrew Cooper
> ; Ian Jackson ; Tim
> (Xen.org) ; Julie
On Thu, Aug 02, 2018 at 02:23:23AM -0600, Jan Beulich wrote:
> >>> On 02.08.18 at 09:46, wrote:
> >> From: Roger Pau Monne [mailto:roger@citrix.com]
> >> Sent: Wednesday, August 1, 2018 7:04 PM
> >> --- a/docs/misc/xen-command-line.markdown
> >> +++ b/docs/misc/xen-command-line.markdown
> >>
flight 125750 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/125750/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 1d802e234e813a6726f4c6fd161ae9bd146bc552
baseline version:
ovmf 6fb8b96d9bab1281f0208
84 matches
Mail list logo
