[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ACPI/UEFI support for Xen/ARM status?


  • To: Elliott Mitchell <ehem+xen@xxxxxxx>
  • From: Bertrand Marquis <Bertrand.Marquis@xxxxxxx>
  • Date: Mon, 15 Nov 2021 10:06:20 +0000
  • Accept-language: en-GB, en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=arm.com; dmarc=pass action=none header.from=arm.com; dkim=pass header.d=arm.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=IFw2j1tjf25NBA1dYggn3WSIt5R0FrngJH9QcQcSJho=; b=YFJoej2vH4gZTXk3EpRYEDugmcUysoNUowAHyo9wE7GokT36tQgWM3LKr8Vf1BxLPDgMgEbThxYcSkBdnNIB7wo5O7Ae87ZZ4ynjUa3ytEWlxFkBgqwPxrMP9qj061SrG1EKOpShus60h7UBGmPnxJI14M7lydjLgUbf3ls8iDwI+4906936qggtvgnkOCW/1IEEbCwgAoM3joPr+GYnws/GxY0Rvm3fx7g2Mmvxux4NSIJqO0xZhceediBsHcApbFNuoTeq2Eowzj3vJAealCwyGi6pd2e2KbaRWTxPlvri1VcxzMaEGkibPZUkd363WSplz93aaxohgBMDw+NXGw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=hrkq12iBx/RKwpHwd3IJlG86tGiigHb2mVQoCyc5Jc05ntMnj/cXvz5qGiZgsfCnLUDcmwbedBFwAmPS1EpvXIik5zpfuXshU/KcWPt5+qv68gWLqhkDK+UbL32INnAZc/ODK3nA8x2w06rB8Mh1Vo8Vu4b5SVpRNki31EB3Ftopn6Y9jCBP28GV6kliGI5Nz5orR9r8ldLNj8XSGBslf993P9H61y0CSifT6iIqmTNrOxYdCZPyxfwD5DsH/ebafjpwlcDYE7pXM7R2Zbtk9G5GKm1i1Wb1fJYDrW5g0J0Wl/0/p8ifLzDF+Qu0zHgdlaqAob5BgIhEewlnViaFug==
  • Authentication-results-original: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=arm.com;
  • Cc: Julien Grall <julien.grall.oss@xxxxxxxxx>, Henry Wang <Henry.Wang@xxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Mon, 15 Nov 2021 10:06:45 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
  • Nodisclaimer: true
  • Original-authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=arm.com;
  • Thread-index: AQHX133CsQ6+s6pLvkyQczdSyBF05qv/ZG4AgACk+gCAAAUHAIAADdAAgAAM2gCAADyfAIAADw8AgAAGlgCAAAfxAIAAIj8AgAO8VYA=
  • Thread-topic: ACPI/UEFI support for Xen/ARM status?

Hi Elliott,

> On 13 Nov 2021, at 01:03, Elliott Mitchell <ehem+xen@xxxxxxx> wrote:
> 
> On Fri, Nov 12, 2021 at 11:00:54PM +0000, Julien Grall wrote:
>> On Fri, 12 Nov 2021 at 22:32, Elliott Mitchell <ehem+xen@xxxxxxx> wrote:
>>>> My preference is to introduce a per-platform quirk (I believe Stefano was 
>>>> happy
>>>> with this). The advantage is we could get ACPI support for your board 
>>>> hopefully
>>>> merged quicker.
>>> 
>>> This could be workable as a temporary workaround.  Longer term I suspect
>>> it might well be rather better to *fully* tackle the issue *now*.
>>> Otherwise this seems likely to turn into a database of board-specific
>>> hacks for hundreds or thousands of devices.
>> 
>> As usual, you have to find a balance between cost vs benefits.
>> 
>> If you look at the Device-Tree side, we don' t have many platforms
>> requiring quirks.
>> In particular, the DMA is so far strictly limited to a single platform (RPI).
>> So I would be surprised if we suddenly require tons of quirks when using
>> ACPI.
> 
> Presently the DMA quirk would be the only consumer, but there will likely
> be other consumers later.  Might there be few device-tree quirks due to a
> short list of platforms?  Might full ACPI support vastly increase
> Xen/ARM's target audience?  (partially ACPI so complex to support so many
> varied devices)

We have been looking at the possibility to have ACPI support in Xen.
The main problem with that is the cost in lines of code in Xen which would be 
high
and as a consequence the maintenance cost would be high.
So if anything is done it must stay properly limited using ifdefs to make sure 
people
needing a “small” xen can still have one.

Now I am on the same side as Julien, I would be very happy to help reviewing if 
you
decide to do the work :-)

> 
> I do concede a device-quirk is reasonable for the short-term.  Presently
> I don't know where to look for better matching targets, so I'm trapped in
> a cave with no light.

What is your need exactly ? A target with frame buffer support ?

Regards
Bertrand

> 
> 
> -- 
> (\___(\___(\______          --=> 8-) EHM <=--          ______/)___/)___/)
> \BS (    |         ehem+sigmsg@xxxxxxx  PGP 87145445         |    )   /
>  \_CS\   |  _____  -O #include <stddisclaimer.h> O-   _____  |   /  _/
> 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.