xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Jiandi An <anjiandi@codeaurora.org>
To: xen-devel@lists.xen.org
Cc: Julien Grall <julien.grall@arm.com>,
	sstabellini@kernel.org, anjiandi@codeaurora.org,
	shankerd@codeaurora.org
Subject: Xen: ARM: Support to map mmio region specified in static ACPI tables
Date: Wed, 14 Dec 2016 02:17:18 -0600	[thread overview]
Message-ID: <5851000E.6020903@codeaurora.org> (raw)

Hi Guys,

Xen currently does not handle mapping mmio regions specified in standard static ACPI tables such as BERT, TPM2, GT block, IORT, HEST, etc.  There has been some initial discussions on using whitelist and leave it up to the individual drivers in dom0 who need the particular region in particular ACPI static table to be mapped to add the support of calling back to XEN to request the mapping.  Just want to get the discussion started and gather consensus on this approach.  This means in each driver in dom0 logic is inserted to check for if running under Xen being dom0, then call hypercall to XEN to request mapping.  Maintainers for individual drivers (BERT driver, TPM driver, etc) may not like this idea for inserting XEN specific checking and mapping call in the driver right?

Thanks.

-- 
Jiandi An
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

             reply	other threads:[~2016-12-14  8:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-14  8:17 Jiandi An [this message]
2016-12-19 23:39 ` Xen: ARM: Support to map mmio region specified in static ACPI tables Stefano Stabellini
2016-12-20  7:58   ` Jan Beulich
2016-12-20 22:55     ` Stefano Stabellini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5851000E.6020903@codeaurora.org \
    --to=anjiandi@codeaurora.org \
    --cc=julien.grall@arm.com \
    --cc=shankerd@codeaurora.org \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).