>>> On 13.10.17 at 04:02, wrote:
> On 17-10-12 03:43:26, Jan Beulich wrote:
>> >>> On 12.10.17 at 06:33, wrote:
>> > On 17-10-11 07:38:52, Jan Beulich wrote:
>> >> >>> On 08.10.17 at 09:23, wrote:
>> >> > --- a/xen/arch/x86/psr.c
>> >> > +++ b/xen/arch/x86/psr.c
>> >> > @@ -138,6 +138,12 @@ stat
>>> On 12.10.17 at 18:06, wrote:
> On 12/10/17 16:53, Jan Beulich wrote:
> On 02.10.17 at 18:13, wrote:
>>> The triple-fault reboot method stays as is, to avoid the int3 possibly
>>> getting
>>> moved relative to the lidt.
>> Aren't asm volatile()s ordered wrt to one another?
>
> From the d
flight 114384 xen-4.8-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/114384/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-multivcpu broken in 114313
Tests
ping
On 10/04/2017 09:50 AM, Oleksandr Andrushchenko wrote:
gentle reminder
On 09/26/2017 02:35 PM, Oleksandr Andrushchenko wrote:
Clemens, Sakamoto-san,
could you please review the below if you by chance have a minute?
Thank you,
Oleksandr
On 09/19/2017 11:57 AM, Oleksandr Andrushchenko wr
Linus,
Please git pull the following tag:
git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
for-linus-4.14c-rc5-tag
xen: fixes for 4.14 rc5
It contains a minor fix correcting the cpu hotplug name for Xen guests.
Thanks.
Juergen
arch/x86/xen/enlighten.c | 4 ++--
1 file changed, 2
flight 114395 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/114395/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt-xsm 14 saverestore-support-checkfail like 114088
test-armhf-armhf-libvirt 14 saveresto
branch xen-unstable
xenbranch xen-unstable
job test-amd64-amd64-xl-pvh-amd
testid guest-start
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://git.qemu.
flight 114372 xen-4.9-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/114372/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl broken in 114312
test-armhf-armhf-xl-multivc
On 17-10-12 03:43:26, Jan Beulich wrote:
> >>> On 12.10.17 at 06:33, wrote:
> > On 17-10-11 07:38:52, Jan Beulich wrote:
> >> >>> On 08.10.17 at 09:23, wrote:
> >> > --- a/xen/arch/x86/psr.c
> >> > +++ b/xen/arch/x86/psr.c
> >> > @@ -138,6 +138,12 @@ static const struct feat_props {
> >> >
> >>
flight 114368 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/114368/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf broken
build-armhf 4 host-instal
> On Oct 12, 2017, at 4:27 PM, Daniel Kiper wrote:
>
>> On Thu, Oct 12, 2017 at 03:50:06PM -0500, Doug Goldstein wrote:
>> From: David Esler
>>
>> In 9180f5365524 a change was made to the send_chr function to take in
>> C-strings and print out a character at a time until a NULL was
>> encounte
flight 114362 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/114362/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-rumprun-amd64 17 rumprun-demo-xenstorels/xenstorels.repeat
fail REGR. vs. 114297
Tests wh
branch xen-unstable
xenbranch xen-unstable
job test-amd64-amd64-xl-pvh-intel
testid guest-start
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://xenbits
flight 114357 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/114357/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-cubietruck 17 guest-start.2 fail REGR. vs. 114204
Tests which did no
On Thu, Oct 12, 2017 at 09:56:01PM +0100, Andrew Cooper wrote:
> On 12/10/2017 21:50, Doug Goldstein wrote:
> > From: David Esler
> >
> > The send_chr function sends an entire C-string and not one character and
> > doesn't necessarily just send it over the serial UART anymore so rename
> > it to p
On Thu, Oct 12, 2017 at 03:50:06PM -0500, Doug Goldstein wrote:
> From: David Esler
>
> In 9180f5365524 a change was made to the send_chr function to take in
> C-strings and print out a character at a time until a NULL was
> encountered. However there is no code to increment the current character
On 10/12/2017 5:14 PM, Julien Grall wrote:
On 12/10/17 12:22, Manish Jaggi wrote:
Hi Julien,
Why do you omit parts of mail where I have asked a question , please
avoid skiping that removes the context.
I believe I answered it just after because you asked twice the same
thing. So may I
ACPI/IORT Support in Xen.
--
I had sent out patch series [0] to hide smmu from Dom0 IORT. Extending
the scope
and including all that is required to support ACPI/IORT in Xen.
Presenting for review
first _draft_ of design of ACPI/IORT support in Xen. Not compl
On 12/10/2017 21:50, Doug Goldstein wrote:
> From: David Esler
>
> The send_chr function sends an entire C-string and not one character and
> doesn't necessarily just send it over the serial UART anymore so rename
> it to print_err so that its closer in name to what it does.
>
> Reviewed-by: Doug
On 12/10/2017 21:50, Doug Goldstein wrote:
> From: David Esler
>
> In 9180f5365524 a change was made to the send_chr function to take in
> C-strings and print out a character at a time until a NULL was
> encountered. However there is no code to increment the current character
> position resulting
From: David Esler
In 9180f5365524 a change was made to the send_chr function to take in
C-strings and print out a character at a time until a NULL was
encountered. However there is no code to increment the current character
position resulting in an endless loop of the first character. This adds
a
From: David Esler
The send_chr function sends an entire C-string and not one character and
doesn't necessarily just send it over the serial UART anymore so rename
it to print_err so that its closer in name to what it does.
Reviewed-by: Doug Goldstein
Signed-off-by: David Esler
---
xen/arch/x8
On Wed, Oct 11, 2017 at 01:30:15PM -0700, Thomas Garnier wrote:
> Provide an option to default visibility to hidden except for key
> symbols. This option is disabled by default and will be used by x86_64
> PIE support to remove errors between compilation units.
>
> The default visibility is also e
On 10/12/2017 03:27 PM, Andrew Cooper wrote:
> On 12/10/17 20:11, Boris Ostrovsky wrote:
>> On 10/06/2017 10:32 AM, Josh Poimboeuf wrote:
>>> On Thu, Oct 05, 2017 at 04:35:03PM -0400, Boris Ostrovsky wrote:
> #ifdef CONFIG_PARAVIRT
> +/*
> + * Paravirt alternatives are applied much ear
On 12/10/17 20:11, Boris Ostrovsky wrote:
> On 10/06/2017 10:32 AM, Josh Poimboeuf wrote:
>> On Thu, Oct 05, 2017 at 04:35:03PM -0400, Boris Ostrovsky wrote:
#ifdef CONFIG_PARAVIRT
+/*
+ * Paravirt alternatives are applied much earlier than normal
alternatives.
+ * They a
pfn 0 is a legitimate (albeit unlikely) frame to use, so skipping it is wrong.
This behaviour appears to exists simply to cover the fact that zero is the
default value of an uninitialised field in dom.
ARM already clears the frames at the point that the pfns are allocated,
meaning that the added c
libxl always uses xc_dom_gnttab_init(), which internally calls
xc_dom_gnttab{_hvm,}_seed() to set up the grants point at the console and
xenstore rings. For HVM guests, libxl then asks Xen for the information set
up previously, and calls xc_dom_gnttab_hvm_seed() a second time, which is
wasteful.
alloc_magic_pages() is renamed to alloc_magic_pages_pv() to mirror its
alloc_magic_pages_hvm() counterpart. Delete a redundant comment, introduce
some newlines clarity, and remove a logically dead allocation of shared info.
Signed-off-by: Andrew Cooper
Reviewed-by: Roger Pau Monné
Acked-by: Wei
A git tree version is available:
http://xenbits.xen.org/gitweb/?p=people/andrewcoop/xen.git;a=shortlog;h=refs/heads/dombuilder-gnt-v2
Changes in v2: Mainly a rebase over c/s 5b42c82f "tools/libxc: Fix domid
parameter types", and fixup from review comments. See individual patches for
details
And
Recent changes in grant table configuration have caused calls to
xc_dom_gnttab_init() to fail if not proceeded with a call to
xc_domain_set_gnttab_limits(). This is backwards from the point of view of
3rd party dombuilder users.
Add max_{grant,maptrack}_frames parameters to struct xc_dom_image, a
The sole use of xc_dom_translated() and xc_dom_p2m() outside of the domain
builder is for libxl_dom() to translate the console and xenstore pfns back
into useful values. PV guest pfns are only interesting to the domain builder,
and gfns are the address space used by all other hypercalls.
Renaming
On 10/06/2017 10:32 AM, Josh Poimboeuf wrote:
> On Thu, Oct 05, 2017 at 04:35:03PM -0400, Boris Ostrovsky wrote:
>>> #ifdef CONFIG_PARAVIRT
>>> +/*
>>> + * Paravirt alternatives are applied much earlier than normal alternatives.
>>> + * They are only applied when running on a hypervisor. They rep
On 12/10/17 19:54, Bhupinder Thakur wrote:
> On 5 October 2017 at 15:07, Wei Liu wrote:
>> On Wed, Oct 04, 2017 at 09:58:32PM -0400, Konrad Rzeszutek Wilk wrote:
>>> I get this when compiling under ARM32 (Ubuntu 15.04,
>>> gcc (Ubuntu/Linaro 4.9.2-10ubuntu13) 4.9.2):
>>>
>>> libxl_console.c: In fu
On 5 October 2017 at 15:07, Wei Liu wrote:
> On Wed, Oct 04, 2017 at 09:58:32PM -0400, Konrad Rzeszutek Wilk wrote:
>> I get this when compiling under ARM32 (Ubuntu 15.04,
>> gcc (Ubuntu/Linaro 4.9.2-10ubuntu13) 4.9.2):
>>
>> libxl_console.c: In function ‘libxl__device_vuart_add’:
>> libxl_console
On Fri, Oct 6, 2017 at 6:54 AM, Andrew Cooper wrote:
> On 06/10/17 14:33, Jan Beulich wrote:
>> All,
>>
>> with the goal of releasing around the end of the month, please point
>> out backport candidates you find missing from the respective staging
>> branches, but which you consider relevant. Note
flight 114426 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/114426/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 13 migrate-support-checkfail never pass
test-armhf-armhf-xl 1
On Thu, Oct 12, 2017 at 08:45:44PM +0800, Haozhong Zhang wrote:
> On 10/10/17 12:05 -0400, Konrad Rzeszutek Wilk wrote:
> > On Tue, Sep 12, 2017 at 11:15:09AM +0800, Haozhong Zhang wrote:
> > > On 09/11/17 11:52 -0700, Stefano Stabellini wrote:
> > > > CC'ing xen-devel, and the Xen tools and x86 ma
On Thu, Oct 12, 2017 at 3:10 AM, Alexandru Isaila
wrote:
> This patch adds the old value param and the onchangeonly option
> to the VM_EVENT_REASON_MOV_TO_MSR event.
>
> The param was added to the vm_event_mov_to_msr struct and to the
> hvm_monitor_msr function. Finally I've changed the bool_t par
On Thu, 12 Oct 2017, Paul Durrant wrote:
> > -Original Message-
> > From: Gerd Hoffmann [mailto:kra...@redhat.com]
> > Sent: 12 October 2017 10:26
> > To: Paul Durrant ; 'Stefano Stabellini'
> > ; Anthony Perard
> > Cc: qemu-de...@nongnu.org; xen-de...@lists.xenproject.org; Owen Smith
> >
Hi all,
for 4.9.1 the XSA status is
XSA 226 : Some patches not applied => check
There is an extra chunk in the tree: see xsa226.png
XSA 227 : All patches found (no need to check)
XSA 228 : All patches found (no need to check)
XSA 229 : No patch found => check
Linux only => no issue
XSA 230 : A
Hi
What is the status of creating a shim to abstract secure boot signing for Xen
(to leverage MSFT 3rd party, e.g)?
Thanks
-Bill
> -Original Message-
> From: Daniel Kiper [mailto:daniel.ki...@oracle.com]
> Sent: Tuesday, May 16, 2017 4:05 AM
> To: Bill Jacobs (billjac)
> Cc: george.dun..
Hi Sameer,
Given this is all Arm specific. I am not sure why people like Andrew,
Jan have been added.
Please use scripts/get_maintainers to find the list of maintainers per
patches and avoid to CC all of them on each patches.
On 21/09/17 01:37, Sameer Goel wrote:
This driver follows an app
On 10/12/2017 10:34 AM, Thomas Garnier wrote:
On Wed, Oct 11, 2017 at 2:34 PM, Tom Lendacky wrote:
On 10/11/2017 3:30 PM, Thomas Garnier wrote:
Changes:
- patch v1:
- Simplify ftrace implementation.
- Use gcc mstack-protector-guard-reg=%gs with PIE when possible.
- rfc v3:
A previous patch added support for priv-mapping guest resources directly
(rather than having to foreign-map, which requires P2M modification for
HVM guests).
This patch makes use of the new API to seed the guest grant table unless
the underlying infrastructure (i.e. privcmd) doesn't support it, in
This patch allows grant table frames to be mapped using the
XENMEM_acquire_resource memory op.
Signed-off-by: Paul Durrant
---
Cc: Andrew Cooper
Cc: George Dunlap
Cc: Ian Jackson
Cc: Jan Beulich
Cc: Konrad Rzeszutek Wilk
Cc: Stefano Stabellini
Cc: Tim Deegan
Cc: Wei Liu
v10:
- Addressed
A subsequent patch will remove the current implicit limitation on creation
of ioreq servers which is due to the allocation of gfns for the ioreq
structures and buffered ioreq ring.
It will therefore be necessary to introduce an explicit limit and, since
this limit should be small, it simplifies th
Certain memory resources associated with a guest are not necessarily
present in the guest P2M.
This patch adds the boilerplate for new memory op to allow such a resource
to be priv-mapped directly, by either a PV or HVM tools domain.
NOTE: Whilst the new op is not intrinsicly specific to the x86
This patch re-works much of the ioreq server initialization and teardown
code:
- The hvm_map/unmap_ioreq_gfn() functions are expanded to call through
to hvm_alloc/free_ioreq_gfn() rather than expecting them to be called
separately by outer functions.
- Several functions now test the validity o
... XENMEM_resource_ioreq_server
This patch adds support for a new resource type that can be mapped using
the XENMEM_acquire_resource memory op.
If an emulator makes use of this resource type then, instead of mapping
gfns, the IOREQ server will allocate pages from the heap. These pages
will never
A previous patch introduced a new HYPERVISOR_memory_op to acquire guest
resources for direct priv-mapping.
This patch adds new functionality into libxenforeignmemory to make use
of a new privcmd ioctl [1] that uses the new memory op to make such
resources available via mmap(2).
[1]
http://xenbit
...to allow the calling domain to prevent translation of specified l1e
value.
Despite what the comment in public/xen.h might imply, specifying a
command value of MMU_NORMAL_PT_UPDATE will not simply update an l1e with
the specified value. Instead, mod_l1_entry() tests whether foreign_dom
has PG_tr
A subsequent patch will introduce a new scheme to allow an emulator to
map ioreq server pages directly from Xen rather than the guest P2M.
This patch lays the groundwork for that change by deferring mapping of
gfns until their values are requested by an emulator. To that end, the
pad field of the
This series introduces support for direct mapping of guest resources.
The resources are:
- IOREQ server pages
- Grant tables
v10:
- Responded to comments from Jan.
v9:
- Change to patch #1 only.
v8:
- Re-ordered series and dropped two patches that have already been
committed.
v7:
- Fi
This patch adjusts the ioreq server code to use type-safe gfn_t values
where possible. No functional change.
Signed-off-by: Paul Durrant
Reviewed-by: Roger Pau Monné
Reviewed-by: Wei Liu
Acked-by: Jan Beulich
---
Cc: Andrew Cooper
---
xen/arch/x86/hvm/ioreq.c | 44 +++
By using a static inline stub in private.h for OS where this functionality
is not implemented, the various duplicate stubs in the OS-specific source
modules can be avoided.
Signed-off-by: Paul Durrant
Reviewed-by: Roger Pau Monné
Acked-by: Wei Liu
---
Cc: Ian Jackson
v4:
- Removed extraneous
On 12/10/17 16:53, Jan Beulich wrote:
On 02.10.17 at 18:13, wrote:
>> The triple-fault reboot method stays as is, to avoid the int3 possibly
>> getting
>> moved relative to the lidt.
> Aren't asm volatile()s ordered wrt to one another?
>From the docs
"Note that the compiler can move even v
>>> On 02.10.17 at 18:13, wrote:
> @@ -518,26 +522,29 @@ static void invalidate_shadow_ldt(struct vcpu *v, int
> flush)
> if ( v->arch.pv_vcpu.shadow_ldt_mapcnt == 0 )
> goto out;
>
> -v->arch.pv_vcpu.shadow_ldt_mapcnt = 0;
> pl1e = pv_ldt_ptes(v);
>
> for ( i = 0;
>>> On 02.10.17 at 18:13, wrote:
> The triple-fault reboot method stays as is, to avoid the int3 possibly getting
> moved relative to the lidt.
Aren't asm volatile()s ordered wrt to one another?
> --- a/xen/include/asm-x86/desc.h
> +++ b/xen/include/asm-x86/desc.h
> @@ -197,6 +197,26 @@ DECLARE_
On 2017.10.12 at 08:34 -0700, Thomas Garnier wrote:
> On Wed, Oct 11, 2017 at 2:34 PM, Tom Lendacky wrote:
> > On 10/11/2017 3:30 PM, Thomas Garnier wrote:
> >> Changes:
> >> - patch v1:
> >> - Simplify ftrace implementation.
> >> - Use gcc mstack-protector-guard-reg=%gs with PIE when po
On 12/10/2017 14:45, Haozhong Zhang wrote:
> Basically, QEMU builds two ROMs for guest, /rom@etc/acpi/tables and
> /rom@etc/table-loader. The former is unstructured to guest, and
> contains all data of guest ACPI. The latter is a BIOSLinkerLoader
> organized as a set of commands, which direct the g
>>> On 02.10.17 at 18:13, wrote:
> No functional change.
>
> Signed-off-by: Andrew Cooper
Reviewed-by: Jan Beulich
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
>>> On 12.10.17 at 17:24, wrote:
> On 12/10/17 16:08, Jan Beulich wrote:
> On 12.10.17 at 15:54, wrote:
>>> --- a/xen/arch/x86/mm/hap/hap.c
>>> +++ b/xen/arch/x86/mm/hap/hap.c
>>> @@ -391,41 +391,24 @@ int hap_set_allocation(struct domain *d, unsigned int
> pages, bool *preempted)
>>> r
>>> On 11.10.17 at 19:52, wrote:
> The Intel manual claims that, "If [certain CPUID bits] are set, the
> processor deprecates FCS and FDS, and the field is saved as h";
> but experimentally it would be more accurate to say, "the field is
> occasionally saved as h". This causes the --rerun
flight 114421 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/114421/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf broken
build-armhf
On Wed, Oct 11, 2017 at 2:34 PM, Tom Lendacky wrote:
> On 10/11/2017 3:30 PM, Thomas Garnier wrote:
>> Changes:
>> - patch v1:
>> - Simplify ftrace implementation.
>> - Use gcc mstack-protector-guard-reg=%gs with PIE when possible.
>> - rfc v3:
>> - Use --emit-relocs instead of -pi
On 12/10/17 16:08, Jan Beulich wrote:
On 12.10.17 at 15:54, wrote:
>> --- a/xen/arch/x86/mm/hap/hap.c
>> +++ b/xen/arch/x86/mm/hap/hap.c
>> @@ -391,41 +391,24 @@ int hap_set_allocation(struct domain *d, unsigned int
>> pages, bool *preempted)
>> return 0;
>> }
>>
>> -static void hap_
>>> On 11.10.17 at 19:52, wrote:
> @@ -884,20 +891,146 @@ int LLVMFuzzerInitialize(int *argc, char ***argv)
> return 0;
> }
>
> -int LLVMFuzzerTestOneInput(const uint8_t *data_p, size_t size)
> +static void setup_fuzz_state(struct fuzz_state *state, const void *data_p,
> size_t size)
> {
>>> On 11.10.17 at 19:52, wrote:
> --- a/tools/fuzz/x86_instruction_emulator/fuzz-emul.c
> +++ b/tools/fuzz/x86_instruction_emulator/fuzz-emul.c
> @@ -22,34 +22,31 @@
>
> #define SEG_NUM x86_seg_none
>
> -/* Layout of data expected as fuzzing input. */
> -struct fuzz_corpus
> +/*
> + * State
On Thu, Oct 12, 2017 at 02:24:23PM +, Ian Jackson wrote:
> osstest service owner writes ("[osstest test] 114342: regressions - trouble:
> blocked/broken/fail/pass"):
> > flight 114342 osstest real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/114342/
> >
> > Regressions :-(
> >
On Thu, Oct 12, 2017 at 02:54:22PM +0100, Andrew Cooper wrote:
> There are currently three functions which write L4 pagetables for Xen, but
> they all behave subtly differently. sh_install_xen_entries_in_l4() in
> particular is catering for two different usecases, which makes the safety of
> the l
>>> On 12.10.17 at 15:54, wrote:
> --- a/xen/arch/x86/mm/hap/hap.c
> +++ b/xen/arch/x86/mm/hap/hap.c
> @@ -391,41 +391,24 @@ int hap_set_allocation(struct domain *d, unsigned int
> pages, bool *preempted)
> return 0;
> }
>
> -static void hap_install_xen_entries_in_l4(struct vcpu *v, mfn_t
On Thu, Oct 12, 2017 at 02:54:21PM +0100, Andrew Cooper wrote:
> Having all of this logic together makes it easier to follow Xen's virtual
> setup across the whole system.
>
> No functional change.
>
> Signed-off-by: Andrew Cooper
Reviewed-by: Wei Liu
_
>>> On 12.10.17 at 15:54, wrote:
> Having all of this logic together makes it easier to follow Xen's virtual
> setup across the whole system.
>
> No functional change.
>
> Signed-off-by: Andrew Cooper
Reviewed-by: Jan Beulich
___
Xen-devel mailin
>>> On 12.10.17 at 15:54, wrote:
> This reverts commit f3b95fd07fdb55b1db091fede1b9a7c71f1eaa1b and
> 1bd39738a5a34f529a610fb275cc83ee5ac7547a.
>
> The following patches (post XSA-243 fixes) requires init_guest_l4_table()
> being common code.
>
> Signed-off-by: Andrew Cooper
Acked-by: Jan Beul
On Thu, Oct 12, 2017 at 02:33:04PM +0100, Julien Grall wrote:
> Hi,
>
> Bringing back this discussion.
>
> On 28/08/17 22:39, Goel, Sameer wrote:
> >
> >
> > On 6/9/2017 3:44 AM, Wei Liu wrote:
> > > On Thu, Jun 08, 2017 at 08:49:01PM +0100, Julien Grall wrote:
> > > > CC the REST maintainers
>
On Thu, Oct 12, 2017 at 02:54:20PM +0100, Andrew Cooper wrote:
> This reverts commit f3b95fd07fdb55b1db091fede1b9a7c71f1eaa1b and
> 1bd39738a5a34f529a610fb275cc83ee5ac7547a.
>
> The following patches (post XSA-243 fixes) requires init_guest_l4_table()
> being common code.
>
> Signed-off-by: Andre
On Thu, Oct 12, 2017 at 5:02 AM, Wei Liu wrote:
>
> FYI all patches except the xentrace one were committed yesterday.
Thank you very much, Wei!
Best,
Meng
--
Meng Xu
Ph.D. Candidate in Computer and Information Science
University of Pennsylvania
http://www.cis.upenn.edu/~mengxu/
osstest service owner writes ("[osstest test] 114342: regressions - trouble:
blocked/broken/fail/pass"):
> flight 114342 osstest real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/114342/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which co
Hi Sameer,
On 21/09/17 01:37, Sameer Goel wrote:
@@ -583,14 +631,13 @@ const struct iommu_ops *iort_iommu_configure(struct
device *dev)
u32 streamid = 0;
if (dev_is_pci(dev)) {
- struct pci_bus *bus = to_pci_dev(dev)->bus;
+ struct pci_dev *pci_device
Hi Sameer,
On 21/09/17 01:37, Sameer Goel wrote:
Add support for parsing IORT table to initialize SMMU devices.
* The code for creating an SMMU device has been modified, so that the SMMU
device can be initialized.
* The NAMED NODE code has been commented out as this will need DOM0 kernel
support
There are currently three functions which write L4 pagetables for Xen, but
they all behave subtly differently. sh_install_xen_entries_in_l4() in
particular is catering for two different usecases, which makes the safety of
the linear mappings hard to follow.
By consolidating the L4 pagetable writi
This reverts commit f3b95fd07fdb55b1db091fede1b9a7c71f1eaa1b and
1bd39738a5a34f529a610fb275cc83ee5ac7547a.
The following patches (post XSA-243 fixes) requires init_guest_l4_table()
being common code.
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
CC: Wei Liu
CC: Julien Grall
These pagetabl
The important change here is in patch 3, which is intended to remove the
correct-but-dangerous-looking construction of linear pagetables slots for
shadowed guests.
Andrew Cooper (3):
Revert "x86/mm: move PV l4 table setup code" and "x86/mm: factor out
pv_arch_init_memory"
x86/mm: Consolida
Having all of this logic together makes it easier to follow Xen's virtual
setup across the whole system.
No functional change.
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
CC: Tim Deegan
CC: George Dunlap
CC: Wei Liu
CC: Julien Grall
---
xen/arch/x86/mm.c | 16 +---
flight 114418 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/114418/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-libvirt 12 guest-start fail REGR. vs. 114299
Tests which
Hi,
On 12/10/17 14:05, Julien Grall wrote:
Hi,
On 21/09/17 01:37, Sameer Goel wrote:
Introduce a common structure to hold the fw (ACPI or DT) defined
configuration for SMMU hw. The current use case is for arm SMMUs. So,
making this architecture specific.
Based on Linux kernel commit 57f98d2f6
Hi,
Bringing back this discussion.
On 28/08/17 22:39, Goel, Sameer wrote:
On 6/9/2017 3:44 AM, Wei Liu wrote:
On Thu, Jun 08, 2017 at 08:49:01PM +0100, Julien Grall wrote:
CC the REST maintainers
On 08/06/2017 20:30, Sameer Goel wrote:
Introduce a memory realloc function.
Signed-off-by:
Hi,
On 21/09/17 01:37, Sameer Goel wrote:
Introduce a common structure to hold the fw (ACPI or DT) defined
configuration for SMMU hw. The current use case is for arm SMMUs. So,
making this architecture specific.
Based on Linux kernel commit 57f98d2f61e1: iommu: Introduce iommu_fwspec
Signed-off
On 10/10/17 12:05 -0400, Konrad Rzeszutek Wilk wrote:
> On Tue, Sep 12, 2017 at 11:15:09AM +0800, Haozhong Zhang wrote:
> > On 09/11/17 11:52 -0700, Stefano Stabellini wrote:
> > > CC'ing xen-devel, and the Xen tools and x86 maintainers.
> > >
> > > On Mon, 11 Sep 2017, Igor Mammedov wrote:
> > >
Hi,
On 21/09/17 01:37, Sameer Goel wrote:
This will be used as a device property to match the DMA capable devices
with the associated SMMU. The header file is a port from linux. The code
was changed to remove the types that were not needed for Xen.
I think you probably want a bit more context
flight 114338 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/114338/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-libvirt-xsm 7 xen-boot fail REGR. vs. 114175
test-amd64-i386-xl-q
Silently assuming DOMID_SELF is unlikely to be a good idea for page
table updates. For PGT_writable pages, though, it seems better to allow
the writes, so the same check isn't being applied there.
Also add blank lines between the individual case blocks.
Signed-off-by: Jan Beulich
--- a/xen/arch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Xen Security Advisory XSA-238
version 2
DMOP map/unmap missing argument checks
UPDATES IN VERSION 2
Public release.
ISSUE DESCRIPTION
=
DMOPs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Xen Security Advisory XSA-237
version 2
multiple MSI mapping issues on x86
UPDATES IN VERSION 2
Public release.
ISSUE DESCRIPTION
=
Multiple
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Xen Security Advisory XSA-242
version 2
page type reference leak on x86
UPDATES IN VERSION 2
Public release.
ISSUE DESCRIPTION
=
The page
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Xen Security Advisory XSA-243
version 3
x86: Incorrect handling of self-linear shadow mappings with translated guests
UPDATES IN VERSION 3
Public release.
ISSUE DESCRIPTION
=
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Xen Security Advisory XSA-244
version 2
x86: Incorrect handling of IST settings during CPU hotplug
UPDATES IN VERSION 2
Public release.
ISSUE DESCRIPTION
===
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Xen Security Advisory XSA-241
version 3
Stale TLB entry due to page type release race
UPDATES IN VERSION 3
Fix ARM build issue in patches.
Public release.
ISSUE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Xen Security Advisory XSA-239
version 2
hypervisor stack leak in x86 I/O intercept code
UPDATES IN VERSION 2
Public release.
ISSUE DESCRIPTION
=
I
>>> On 12.10.17 at 13:31, wrote:
> On 12/10/17 11:01, Jan Beulich wrote:
>> Don't accept anything other than r/w RAM pages and move the paged-out
>> check into the (unlikely) error path following that check.
>>
>> Signed-off-by: Jan Beulich
>
> How does dom0 boot with this change in place? You
1 - 100 of 137 matches
Mail list logo
