>>> On 11.12.17 at 21:26, wrote:
> On 12/11/2017 10:06 AM, Jan Beulich wrote:
> On 08.12.17 at 15:38, wrote:
>>> On 08/12/17 08:03, Tim Deegan wrote:
It should be possible to do something like the misconfigured-entry bit
trick by
On Tue, Dec 12, 2017 at 12:30 AM, George Dunlap wrote:
> On Mon, Dec 11, 2017 at 3:05 PM, Boris Ostrovsky
> wrote:
> > On 12/11/2017 09:36 AM, Meng Xu wrote:
> >> On Mon, Dec 11, 2017 at 8:14 AM, Minjun Hong
> wrote:
> >>>
These duplicate includes have been found with scripts/checkincludes.pl but
they have been removed manually to avoid removing false positives.
Signed-off-by: Pravin Shedge
---
arch/x86/kernel/itmt.c | 1 -
arch/x86/kernel/process.c | 1 -
From: Elena Ufimtseva
It is expected that the symbol has type STT_FUNC in livpatch.ignore.functions
sections, but it is incorrect and results in functions not to be ignored.
To actually ignore functions in livepatch.ignore.functions section, attempt to
find the symbol
flight 117060 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/117060/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 broken
build-amd64-prev
On Mon, Dec 11, 2017 at 06:07:48PM +, Anthony PERARD wrote:
>On Fri, Nov 17, 2017 at 02:24:25PM +0800, Chao Gao wrote:
>> According to VT-d spec Interrupt Remapping and Interrupt Posting ->
>> Interrupt Remapping -> Interrupt Request Formats On Intel 64
>> Platforms, fields of MSI data
On Mon, Dec 11, 2017 at 05:59:08PM +, Anthony PERARD wrote:
>On Fri, Nov 17, 2017 at 02:24:24PM +0800, Chao Gao wrote:
>> Previously, some fields (reserved or unalterable) are filtered by
>> Qemu. This fields are useless for the legacy interrupt format.
>> However, these fields are may
flight 117083 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/117083/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 broken
On Tue, 12 Dec 2017, Julien Grall wrote:
> Hi Stefano,
>
> On 12/08/2017 10:43 PM, Stefano Stabellini wrote:
> > On Fri, 8 Dec 2017, Julien Grall wrote:
> > > On 8 Dec 2017 22:26, "Stefano Stabellini" wrote:
> > >On Fri, 8 Dec 2017, Julien Grall wrote:
> > >
Hi Stefano,
On 12/08/2017 10:43 PM, Stefano Stabellini wrote:
On Fri, 8 Dec 2017, Julien Grall wrote:
On 8 Dec 2017 22:26, "Stefano Stabellini" wrote:
On Fri, 8 Dec 2017, Julien Grall wrote:
> On 06/12/17 12:27, Julien Grall wrote:
> > On
Hi Stefano,
On 12/11/2017 11:37 PM, Stefano Stabellini wrote:
On Thu, 9 Nov 2017, Jan Beulich wrote:
On 09.11.17 at 16:48, wrote:
On 09/11/17 15:47, Jan Beulich wrote:
On 09.11.17 at 16:39, wrote:
What I meant is you would replace the 4
On Thu, 9 Nov 2017, Jan Beulich wrote:
> >>> On 09.11.17 at 16:48, wrote:
> > On 09/11/17 15:47, Jan Beulich wrote:
> > On 09.11.17 at 16:39, wrote:
> >>> What I meant is you would replace the 4 occurrences by
> >>> mfn_to_page(_mfn(...)). If
On Wed, 1 Nov 2017, Julien Grall wrote:
> Most of the users of page_to_mfn and mfn_to_page are either overriding
> the macros to make them work with mfn_t or use mfn_x/_mfn because the
> rest of the function use mfn_t.
>
> So make __page_to_mfn and __mfn_to_page return mfn_t by default.
>
> Only
On Wed, 1 Nov 2017, Julien Grall wrote:
> - Remove spurious ()
> - Add missing spaces
> - Turn 1 << to 1UL <<
> - Rename spfn to smfn and switch to mfn_t
>
> Signed-off-by: Julien Grall
Reviewed-by: Stefano Stabellini
> ---
>
On Wed, 9 Aug 2017, Mirela Simonovic wrote:
> This document contains our draft proposal for implementing "suspend to RAM"
> support for ARM in Xen, as discussed during the last Xen ARM community call.
> It covers the basic suspend to RAM mechanism based on ARM PSCI standard,
> that would allow
flight 117082 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/117082/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 broken
On 08/12/2017 09:49, Jan Beulich wrote:
>> + * The layout of each entry in the memory map table is as follows and no
>> + * padding is used between entries in the array:
>> + *
>> + * 0 ++
>> + *| addr | Base address
>> + * 8 ++
>> + *| size
On 12/11/2017 11:10 AM, Andre Przywara wrote:
Hi,
Hi Andre,
But on the other hand we had PoD naturally already in KVM, so this came
at no cost.
So I believe it would be worth to investigate what the actual impact is
on booting a 32-bit kernel, with emulating s/w ops like KVM does (see
Hi Jan,
On 12/11/2017 10:06 AM, Jan Beulich wrote:
On 08.12.17 at 15:38, wrote:
On 08/12/17 08:03, Tim Deegan wrote:
It should be possible to do something like the misconfigured-entry bit
trick by _allocating_ the memory up-front and building the p2m entries
but only
flight 117057 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/117057/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 broken
Hi,
On 12/10/2017 03:22 PM, Tim Deegan wrote:
At 14:38 + on 08 Dec (1512743913), Julien Grall wrote:
On 08/12/17 08:03, Tim Deegan wrote:
+1 for avoiding the full majesty of PoD if you don't need it.
It should be possible to do something like the misconfigured-entry bit
trick by
flight 117056 seabios real [real]
http://logs.test-lab.xenproject.org/osstest/logs/117056/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm broken
build-i386
flight 117062 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/117062/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 broken
build-i386
flight 117059 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/117059/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 broken
build-i386
On Fri, Nov 17, 2017 at 02:24:25PM +0800, Chao Gao wrote:
> According to VT-d spec Interrupt Remapping and Interrupt Posting ->
> Interrupt Remapping -> Interrupt Request Formats On Intel 64
> Platforms, fields of MSI data register have changed. This patch
> avoids wrongly regarding a remappable
On Fri, Nov 03, 2017 at 11:56:27AM +, Owen Smith wrote:
> Improve the input device model in xenfb, by updating the
> Qemu input handlers and adding a feature to allow for
> raw (unscaled) absolute coordinates to be represented.
>
> Changes:
> * use keycodedb to generate qcode to linux input
flight 117058 linux-4.1 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/117058/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 broken
build-i386
>>> On 11.12.17 at 16:54, wrote:
> On 12/11/2017 03:05 PM, Jan Beulich wrote:
> On 11.12.17 at 15:51, wrote:
>>> On 12/11/2017 02:46 PM, Razvan Cojocaru wrote:
On 12/11/2017 03:36 PM, Jan Beulich wrote:
On 11.12.17 at 13:50,
On Tue, Oct 24, 2017 at 11:19 AM, Petre Pircalabu
wrote:
> From: Razvan Cojocaru
>
> For the default EPT view we have xc_set_mem_access_multi(), which
> is able to set an array of pages to an array of access rights with
> a single hypercall.
On 12/11/2017 06:00 PM, Tamas K Lengyel wrote:
>>> I think Jan was saying that he would ideally like to remove *all* guest
>>> access to altp2m functionality, even what's currently there. The more
>>> extra features we make available to guests, the harder it will be in the
>>> future to argue to
On Mon, Dec 11, 2017 at 8:05 AM, Jan Beulich wrote:
On 11.12.17 at 15:51, wrote:
>> On 12/11/2017 02:46 PM, Razvan Cojocaru wrote:
>>> On 12/11/2017 03:36 PM, Jan Beulich wrote:
>>> On 11.12.17 at 13:50, wrote:
On 12/11/2017 05:54 PM, George Dunlap wrote:
> On 12/11/2017 03:05 PM, Jan Beulich wrote:
> On 11.12.17 at 15:51, wrote:
>>> On 12/11/2017 02:46 PM, Razvan Cojocaru wrote:
On 12/11/2017 03:36 PM, Jan Beulich wrote:
On 11.12.17 at 13:50,
On 12/11/2017 03:05 PM, Jan Beulich wrote:
On 11.12.17 at 15:51, wrote:
>> On 12/11/2017 02:46 PM, Razvan Cojocaru wrote:
>>> On 12/11/2017 03:36 PM, Jan Beulich wrote:
>>> On 11.12.17 at 13:50, wrote:
> On 12/11/2017 12:12 PM, Jan
On Mon, Dec 11, 2017 at 3:05 PM, Boris Ostrovsky
wrote:
> On 12/11/2017 09:36 AM, Meng Xu wrote:
>> On Mon, Dec 11, 2017 at 8:14 AM, Minjun Hong wrote:
>>> Thanks for your answer, George.
>>>
>>> What I want ultimately is cache misses from the
>>> On 11.12.17 at 15:46, wrote:
> Quite likely I'm not grasping the full meaning of your objection,
> however the added code is merely another interface to already existing
> core code - so while admittedly there's room for improvement for the EPT
> code below it, this
>>> On 11.12.17 at 15:50, wrote:
> On 12/11/2017 01:36 PM, Jan Beulich wrote:
> On 11.12.17 at 13:50, wrote:
>>> You argued that we should keep PV linear pagetables, before knowing that
>>> NetBSD used them, in spite of having discovered
On 12/11/2017 02:46 PM, Razvan Cojocaru wrote:
> On 12/11/2017 03:36 PM, Jan Beulich wrote:
> On 11.12.17 at 13:50, wrote:
>>> On 12/11/2017 12:12 PM, Jan Beulich wrote:
>>> On 11.12.17 at 12:06, wrote:
> My suggestion was that we
* Juergen Gross wrote:
> On 11/12/17 11:09, Jan Beulich wrote:
> On 08.12.17 at 16:11, wrote:
> >> Set the boot loader version to 2.14 (0x020e) replacing the wrong 0x0212
> >> which should have been 0x020c.
> >
> > This part of the description has become
>>> On 11.12.17 at 13:50, wrote:
> On 12/11/2017 12:12 PM, Jan Beulich wrote:
> On 11.12.17 at 12:06, wrote:
>>> My suggestion was that we don't break usecases. The Intel usecase
>>> specifically is for an in-guest entity to have full
On 12/11/2017 12:12 PM, Jan Beulich wrote:
On 11.12.17 at 12:06, wrote:
>> On 11/12/17 09:14, Jan Beulich wrote:
>> On 08.12.17 at 13:42, wrote:
On 12/08/2017 02:18 PM, Jan Beulich wrote:
On 24.10.17 at 12:19,
flight 72629 distros-debian-sid real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/72629/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-pvops broken
On 11/12/17 09:14, Jan Beulich wrote:
On 08.12.17 at 13:42, wrote:
>> On 12/08/2017 02:18 PM, Jan Beulich wrote:
>> On 24.10.17 at 12:19, wrote:
HVMOP_altp2m_set_mem_access_multi has been added as a HVMOP (as opposed to
a
On Mon, Dec 11, 2017 at 5:59 AM, Minjun Hong wrote:
> Hello, I'm working on the 'credit scheduler' of Xen.
> And I need to compare CPU cache misses between original Xen and my patching
> version.
> But I failed all attempt even if I have tried many methods by googling.
> When
>>> On 11.12.17 at 12:06, wrote:
> On 11/12/17 09:14, Jan Beulich wrote:
> On 08.12.17 at 13:42, wrote:
>>> On 12/08/2017 02:18 PM, Jan Beulich wrote:
>>> On 24.10.17 at 12:19, wrote:
>
>>> On 08.12.17 at 16:11, wrote:
> Set the boot loader version to 2.14 (0x020e) replacing the wrong 0x0212
> which should have been 0x020c.
This part of the description has become partly stale now with the
new patch 3.
Jan
___
ping
On 11/17/2017 10:08 AM, Oleksandr Andrushchenko wrote:
ping
On 11/02/2017 03:11 PM, Oleksandr Andrushchenko wrote:
Hi, all!
Foreword
This RFC is aimed to introduce support of para-virtualized sound
frontend
driver for Xen [1] and gather opinions from the relevant communities
46 matches
Mail list logo