From mboxrd@z Thu Jan  1 00:00:00 1970
From: Julien Grall <julien.grall@citrix.com>
Subject: Re: Design doc of adding ACPI support for arm64 on Xen
 - version 2
Date: Fri, 7 Aug 2015 11:44:35 +0100
Message-ID: <55C48C13.6050105@citrix.com>
References: <55C413D5.7000709@huawei.com>	<55C4896F.6050409@citrix.com>
	<CAMJs5B8NTnbF-ZAcY+TZhODGe3r=D8hbu2HMQwWFwXMrQaLAMA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <CAMJs5B8NTnbF-ZAcY+TZhODGe3r=D8hbu2HMQwWFwXMrQaLAMA@mail.gmail.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Christoffer Dall <christoffer.dall@linaro.org>
Cc: Hangaohuai <hangaohuai@huawei.com>, Ian Campbell <ian.campbell@citrix.com>, "Huangpeng (Peter)" <peter.huangpeng@huawei.com>, xen-devel <xen-devel@lists.xen.org>, Stefano Stabellini <stefano.stabellini@citrix.com>, Shannon Zhao <shannon.zhao@linaro.org>, Jan Beulich <jbeulich@suse.com>, Shannon Zhao <zhaoshenglong@huawei.com>, Parth Dixit <parth.dixit@linaro.org>
List-Id: xen-devel@lists.xenproject.org

On 07/08/15 11:37, Christoffer Dall wrote:
> On Fri, Aug 7, 2015 at 12:33 PM, Julien Grall <julien.grall@citrix.com> wrote:
>> Hi Shannon,
>>
>> Just some clarification questions.
>>
>> On 07/08/15 03:11, Shannon Zhao wrote:
>>> 3. Dom0 gets grant table and event channel irq information
>>> -----------------------------------------------------------
>>> As said above, we assign the hypervisor_id be "XenVMM" to tell Dom0 that
>>> it runs on Xen hypervisor.
>>>
>>> For grant table, add two new HVM_PARAMs: HVM_PARAM_GNTTAB_START_ADDRESS
>>> and HVM_PARAM_GNTTAB_SIZE.
>>>
>>> For event channel irq, reuse HVM_PARAM_CALLBACK_IRQ and add a new
>>> delivery type:
>>> val[63:56] == 3: val[15:8] is flag: val[7:0] is a PPI (ARM and ARM64
>>> only)
>>
>> Can you describe the content of flag?
>>
>>> When constructing Dom0 in Xen, save these values. Then Dom0 could get
>>> them through hypercall HVMOP_get_param.
>>>
>>> 4. Map MMIO regions
>>> -------------------
>>> Register a bus_notifier for platform and amba bus in Linux. Add a new
>>> XENMAPSPACE "XENMAPSPACE_dev_mmio". Within the register, check if the
>>> device is newly added, then call hypercall XENMEM_add_to_physmap to map
>>> the mmio regions.
>>>
>>> 5. Route device interrupts to Dom0
>>> ----------------------------------
>>> Route all the SPI interrupts to Dom0 before Dom0 booting.
>>
>> Not all the SPI will be routed to DOM0. Some are used by Xen and should
>> never be used by any guest. I have in mind the UART and SMMU interrupts.
>>
>> You will have to find away to skip them nicely. Note that not all the
>> IRQs used by Xen are properly registered when we build DOM0 (see the SMMU).
>>
> Just to clarify; Xen should map all SPIs which are not reserved for
> Xen to Dom0, right?

Right.

-- 
Julien Grall