On 06/04/18 16:10, Boris Ostrovsky wrote:
> On 04/06/2018 09:33 AM, George Dunlap wrote:
>> On Fri, Apr 6, 2018 at 2:12 PM, Juergen Gross wrote:
>>>
>>> So its time for a new XENFEAT_ value then? This would be the least
>>> intrusive way to add such a flag. Something like
>>> XENFEAT_linux_high_rs
On 04/06/2018 09:33 AM, George Dunlap wrote:
> On Fri, Apr 6, 2018 at 2:12 PM, Juergen Gross wrote:
>>
>> So its time for a new XENFEAT_ value then? This would be the least
>> intrusive way to add such a flag. Something like
>> XENFEAT_linux_high_rsdp_address_okay ?
> That sounds reasonable to me.
On Fri, Apr 6, 2018 at 2:12 PM, Juergen Gross wrote:
> On 06/04/18 13:13, George Dunlap wrote:
>> On Fri, Apr 6, 2018 at 11:57 AM, Juergen Gross wrote:
>>> On 06/04/18 12:07, George Dunlap wrote:
On Fri, Apr 6, 2018 at 11:02 AM, Juergen Gross wrote:
> On 06/04/18 11:49, George Dunlap wr
On 06/04/18 13:13, George Dunlap wrote:
> On Fri, Apr 6, 2018 at 11:57 AM, Juergen Gross wrote:
>> On 06/04/18 12:07, George Dunlap wrote:
>>> On Fri, Apr 6, 2018 at 11:02 AM, Juergen Gross wrote:
On 06/04/18 11:49, George Dunlap wrote:
> On Thu, Apr 5, 2018 at 7:33 PM, Boris Ostrovsky
>
On Fri, Apr 6, 2018 at 11:57 AM, Juergen Gross wrote:
> On 06/04/18 12:07, George Dunlap wrote:
>> On Fri, Apr 6, 2018 at 11:02 AM, Juergen Gross wrote:
>>> On 06/04/18 11:49, George Dunlap wrote:
On Thu, Apr 5, 2018 at 7:33 PM, Boris Ostrovsky
wrote:
> On 04/05/2018 01:11 PM, Juer
On 06/04/18 12:07, George Dunlap wrote:
> On Fri, Apr 6, 2018 at 11:02 AM, Juergen Gross wrote:
>> On 06/04/18 11:49, George Dunlap wrote:
>>> On Thu, Apr 5, 2018 at 7:33 PM, Boris Ostrovsky
>>> wrote:
On 04/05/2018 01:11 PM, Juergen Gross wrote:
> On 05/04/18 16:56, George Dunlap wrote:
On 06/04/18 12:13, George Dunlap wrote:
> On Thu, Apr 5, 2018 at 6:11 PM, Juergen Gross wrote:
>>> Option 1: Put the RSDP in lowmem unless we know the guest will use the
>>> address in start_info
>>> Pro: Existing Linux instances boot
>>> Con: Existing BSD instances whose memory is an exact multip
On Thu, Apr 5, 2018 at 6:11 PM, Juergen Gross wrote:
>> Option 1: Put the RSDP in lowmem unless we know the guest will use the
>> address in start_info
>> Pro: Existing Linux instances boot
>> Con: Existing BSD instances whose memory is an exact multiple of 1 GiB
>> will have slightly slower TLB m
On Fri, Apr 6, 2018 at 11:02 AM, Juergen Gross wrote:
> On 06/04/18 11:49, George Dunlap wrote:
>> On Thu, Apr 5, 2018 at 7:33 PM, Boris Ostrovsky
>> wrote:
>>> On 04/05/2018 01:11 PM, Juergen Gross wrote:
On 05/04/18 16:56, George Dunlap wrote:
> On Thu, Apr 5, 2018 at 3:09 PM, Juergen
On 06/04/18 11:49, George Dunlap wrote:
> On Thu, Apr 5, 2018 at 7:33 PM, Boris Ostrovsky
> wrote:
>> On 04/05/2018 01:11 PM, Juergen Gross wrote:
>>> On 05/04/18 16:56, George Dunlap wrote:
On Thu, Apr 5, 2018 at 3:09 PM, Juergen Gross wrote:
> On 05/04/18 15:42, George Dunlap wrote:
>>
On Thu, Apr 5, 2018 at 7:33 PM, Boris Ostrovsky
wrote:
> On 04/05/2018 01:11 PM, Juergen Gross wrote:
>> On 05/04/18 16:56, George Dunlap wrote:
>>> On Thu, Apr 5, 2018 at 3:09 PM, Juergen Gross wrote:
On 05/04/18 15:42, George Dunlap wrote:
> On Thu, Apr 5, 2018 at 2:06 PM, Juergen Gros
On Fri, Apr 6, 2018 at 9:00 AM, Juergen Gross wrote:
> On 05/04/18 20:33, Boris Ostrovsky wrote:
>> On 04/05/2018 01:11 PM, Juergen Gross wrote:
>>> On 05/04/18 16:56, George Dunlap wrote:
On Thu, Apr 5, 2018 at 3:09 PM, Juergen Gross wrote:
> On 05/04/18 15:42, George Dunlap wrote:
On 05/04/18 20:33, Boris Ostrovsky wrote:
> On 04/05/2018 01:11 PM, Juergen Gross wrote:
>> On 05/04/18 16:56, George Dunlap wrote:
>>> On Thu, Apr 5, 2018 at 3:09 PM, Juergen Gross wrote:
On 05/04/18 15:42, George Dunlap wrote:
> On Thu, Apr 5, 2018 at 2:06 PM, Juergen Gross wrote:
Den 05.04.2018 kl. 10:02, skrev Juergen Gross:
The kernel is wrong here. You don't want to take the patches fixing the
issue. That's rather sad as PVH mode was meant to replace PV in the
future, which will remove the need for most of the paravirt ops stuff.
You are just shifting that possibilit
On 04/05/2018 01:11 PM, Juergen Gross wrote:
> On 05/04/18 16:56, George Dunlap wrote:
>> On Thu, Apr 5, 2018 at 3:09 PM, Juergen Gross wrote:
>>> On 05/04/18 15:42, George Dunlap wrote:
On Thu, Apr 5, 2018 at 2:06 PM, Juergen Gross wrote:
> On 05/04/18 15:00, Boris Ostrovsky wrote:
On 05/04/18 16:56, George Dunlap wrote:
> On Thu, Apr 5, 2018 at 3:09 PM, Juergen Gross wrote:
>> On 05/04/18 15:42, George Dunlap wrote:
>>> On Thu, Apr 5, 2018 at 2:06 PM, Juergen Gross wrote:
On 05/04/18 15:00, Boris Ostrovsky wrote:
> On 04/05/2018 08:19 AM, Juergen Gross wrote:
On Thu, Apr 5, 2018 at 3:09 PM, Juergen Gross wrote:
> On 05/04/18 15:42, George Dunlap wrote:
>> On Thu, Apr 5, 2018 at 2:06 PM, Juergen Gross wrote:
>>> On 05/04/18 15:00, Boris Ostrovsky wrote:
On 04/05/2018 08:19 AM, Juergen Gross wrote:
> On 05/04/18 12:06, George Dunlap wrote:
On 05/04/18 15:42, George Dunlap wrote:
> On Thu, Apr 5, 2018 at 2:06 PM, Juergen Gross wrote:
>> On 05/04/18 15:00, Boris Ostrovsky wrote:
>>> On 04/05/2018 08:19 AM, Juergen Gross wrote:
On 05/04/18 12:06, George Dunlap wrote:
> Aren't there flags in the binary somewhere that could
On Thu, Apr 5, 2018 at 2:06 PM, Juergen Gross wrote:
> On 05/04/18 15:00, Boris Ostrovsky wrote:
>> On 04/05/2018 08:19 AM, Juergen Gross wrote:
>>> On 05/04/18 12:06, George Dunlap wrote:
>>>
Aren't there flags in the binary somewhere that could tell the
toolstack / Xen whether the kern
On 05/04/18 15:00, Boris Ostrovsky wrote:
> On 04/05/2018 08:19 AM, Juergen Gross wrote:
>> On 05/04/18 12:06, George Dunlap wrote:
>>
>>> Aren't there flags in the binary somewhere that could tell the
>>> toolstack / Xen whether the kernel in question needs the RSDP table in
>>> lowmem, or whether
On 04/05/2018 08:19 AM, Juergen Gross wrote:
> On 05/04/18 12:06, George Dunlap wrote:
>
>> Aren't there flags in the binary somewhere that could tell the
>> toolstack / Xen whether the kernel in question needs the RSDP table in
>> lowmem, or whether it can be put higher?
> Not really. Analyzing th
On 05/04/18 12:06, George Dunlap wrote:
> On Thu, Apr 5, 2018 at 9:00 AM, Juergen Gross wrote:
>>> These are not just "patches to fix the issue", they are "patches to add
>>> new features" that touch core acpi bits, right? Support for new
>>> hardware and platforms and such are not normally part
On Thu, Apr 5, 2018 at 11:06 AM, George Dunlap wrote:
> The fact is, that as it stands, a user could have a perfectly working
> system with Xen 4.10 and a load of PVH guests running stock Linux
> 4.15, and then upgrade to Xen 4.11 and have all those guests break for
> no apparent reason. That's a
On Thu, Apr 5, 2018 at 9:00 AM, Juergen Gross wrote:
>> These are not just "patches to fix the issue", they are "patches to add
>> new features" that touch core acpi bits, right? Support for new
>> hardware and platforms and such are not normally part of the stable
>> kernel patches at all (with
On 05/04/18 09:14, Greg KH wrote:
> On Thu, Apr 05, 2018 at 09:02:27AM +0200, Juergen Gross wrote:
>> On 05/04/18 08:33, Greg KH wrote:
>>> On Wed, Apr 04, 2018 at 06:32:17PM +0200, Juergen Gross wrote:
On 04/04/18 17:42, Greg KH wrote:
> On Wed, Apr 04, 2018 at 05:12:32PM +0200, Juergen G
On Thu, Apr 05, 2018 at 09:02:27AM +0200, Juergen Gross wrote:
> On 05/04/18 08:33, Greg KH wrote:
> > On Wed, Apr 04, 2018 at 06:32:17PM +0200, Juergen Gross wrote:
> >> On 04/04/18 17:42, Greg KH wrote:
> >>> On Wed, Apr 04, 2018 at 05:12:32PM +0200, Juergen Gross wrote:
> On 04/04/18 16:46,
On 05/04/18 08:33, Greg KH wrote:
> On Wed, Apr 04, 2018 at 06:32:17PM +0200, Juergen Gross wrote:
>> On 04/04/18 17:42, Greg KH wrote:
>>> On Wed, Apr 04, 2018 at 05:12:32PM +0200, Juergen Gross wrote:
On 04/04/18 16:46, Greg KH wrote:
> On Wed, Apr 04, 2018 at 04:30:30PM +0200, Juergen G
On Wed, Apr 04, 2018 at 06:32:17PM +0200, Juergen Gross wrote:
> On 04/04/18 17:42, Greg KH wrote:
> > On Wed, Apr 04, 2018 at 05:12:32PM +0200, Juergen Gross wrote:
> >> On 04/04/18 16:46, Greg KH wrote:
> >>> On Wed, Apr 04, 2018 at 04:30:30PM +0200, Juergen Gross wrote:
> On 04/04/18 16:27,
On 04/04/18 17:42, Greg KH wrote:
> On Wed, Apr 04, 2018 at 05:12:32PM +0200, Juergen Gross wrote:
>> On 04/04/18 16:46, Greg KH wrote:
>>> On Wed, Apr 04, 2018 at 04:30:30PM +0200, Juergen Gross wrote:
On 04/04/18 16:27, Greg KH wrote:
> On Wed, Apr 04, 2018 at 12:38:43PM +0200, Juergen G
On Wed, Apr 04, 2018 at 05:12:32PM +0200, Juergen Gross wrote:
> On 04/04/18 16:46, Greg KH wrote:
> > On Wed, Apr 04, 2018 at 04:30:30PM +0200, Juergen Gross wrote:
> >> On 04/04/18 16:27, Greg KH wrote:
> >>> On Wed, Apr 04, 2018 at 12:38:43PM +0200, Juergen Gross wrote:
> Please add the pat
On 04/04/18 16:46, Greg KH wrote:
> On Wed, Apr 04, 2018 at 04:30:30PM +0200, Juergen Gross wrote:
>> On 04/04/18 16:27, Greg KH wrote:
>>> On Wed, Apr 04, 2018 at 12:38:43PM +0200, Juergen Gross wrote:
Please add the patches:
commit 038bac2b02989acf1fc938cedcb7944c02672b9f upstream
On Wed, Apr 04, 2018 at 04:30:30PM +0200, Juergen Gross wrote:
> On 04/04/18 16:27, Greg KH wrote:
> > On Wed, Apr 04, 2018 at 12:38:43PM +0200, Juergen Gross wrote:
> >> Please add the patches:
> >>
> >> commit 038bac2b02989acf1fc938cedcb7944c02672b9f upstream
> >> commit dfc9327ab7c99bc13e1210644
On 04/04/18 16:27, Greg KH wrote:
> On Wed, Apr 04, 2018 at 12:38:43PM +0200, Juergen Gross wrote:
>> Please add the patches:
>>
>> commit 038bac2b02989acf1fc938cedcb7944c02672b9f upstream
>> commit dfc9327ab7c99bc13e12106448615efba833886b upstream
>> commit b17d9d1df3c33a4f1d2bf397e2257aecf9dc56d4
On Wed, Apr 04, 2018 at 12:38:43PM +0200, Juergen Gross wrote:
> Please add the patches:
>
> commit 038bac2b02989acf1fc938cedcb7944c02672b9f upstream
> commit dfc9327ab7c99bc13e12106448615efba833886b upstream
> commit b17d9d1df3c33a4f1d2bf397e2257aecf9dc56d4 upstream
>
> to the 4.15 and 4.16 stab
Please add the patches:
commit 038bac2b02989acf1fc938cedcb7944c02672b9f upstream
commit dfc9327ab7c99bc13e12106448615efba833886b upstream
commit b17d9d1df3c33a4f1d2bf397e2257aecf9dc56d4 upstream
to the 4.15 and 4.16 stable kernels.
Those patches are needed to boot Linux as PVH guest on recent Xe
35 matches
Mail list logo