All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manish Jaggi <mjaggi@caviumnetworks.com>
To: "Julien Grall" <julien.grall@linaro.org>,
	"Roger Pau Monné" <roger.pau@citrix.com>
Cc: edgar.iglesias@xilinx.com,
	Stefano Stabellini <sstabellini@kernel.org>,
	Jan Beulich <JBeulich@suse.com>, Wei Chen <Wei.Chen@arm.com>,
	Steve Capper <Steve.Capper@arm.com>,
	Andre Przywara <andre.przywara@arm.com>,
	manish.jaggi@caviumnetworks.com,
	Punit Agrawal <punit.agrawal@arm.com>,
	vikrams@qti.qualcomm.com, okaya@qti.qualcomm.com, "Goel,
	Sameer" <sgoel@qti.qualcomm.com>,
	xen-devel <xen-devel@lists.xenproject.org>,
	Dave P Martin <Dave.Martin@arm.com>,
	Vijaya Kumar K <Vijaya.Kumar@caviumnetworks.com>
Subject: Re: Notes from PCI Passthrough design discussion at Xen Summit
Date: Thu, 20 Jul 2017 16:30:30 +0530	[thread overview]
Message-ID: <b8113dbf-e01e-1834-366c-53376a23e0be@caviumnetworks.com> (raw)
In-Reply-To: <0739d17a-ab20-be39-76b5-ce4d36ed0037@linaro.org>

HI Julien,

On 7/20/2017 4:11 PM, Julien Grall wrote:
>
>
> On 20/07/17 10:32, Manish Jaggi wrote:
>> Hi Roger,
>>
>> On 7/20/2017 1:54 PM, Roger Pau Monné wrote:
>>> On Thu, Jul 20, 2017 at 09:24:36AM +0530, Manish Jaggi wrote:
>>>> Hi Punit,
>>>>
>>>> On 7/19/2017 8:11 PM, Punit Agrawal wrote:
>>>>> I took some notes for the PCI Passthrough design discussion at Xen
>>>>> Summit. Due to the wide range of topics covered, the notes got 
>>>>> sparser
>>>>> towards the end of the session. I've tried to attribute names against
>>>>> comments but have very likely got things mixed up. Apologies in
>>>>> advance.
>>>> Was curious if any discussions happened on the RC Emu (config space
>>>> emulation) as per slide 18
>>>> https://schd.ws/hosted_files/xendeveloperanddesignsummit2017/76/slides.pdf 
>>>>
>>>>
>>> Part of this is already posted on the list (ATM for x86 only) but the
>>> PCI specification (and therefore the config space emulation) is not
>>> tied to any arch:
>>>
>>> https://lists.xenproject.org/archives/html/xen-devel/2017-06/msg03698.html 
>>>
>>>
>> From the summary, I have a  questions on
>> "
>>  - Roger: Registering config space with Xen before device discovery
>>   will allow the hypervisor to set access traps for certain
>>  functionality as appropriate"
>>
>> Traps will do emulation or something else ?
>>  Is the config space emulation only for DomU or it for Dom0 as well ?
>> Slide 18 shows only for DomU ?
>
> My slides are not meant to be read without the talk. In this 
> particular case, this is only explaining how passthrough will work for 
> DomU.
>
Thanks for clarification.
Ah ok, The single slide created confusion, It would be nice if you have 
added one more describing dom0 config access. I will wait for the video 
to get posted.
> Roger series is at the moment focusing on emulating a fully ECAM 
> compliant hostbridge for the hardware domain. This is because Xen and 
> the hardware domain should not access the configuration space at the 
> same time. 
Yes as discussed on this topic on list few weeks back.
> We may also perform some tasks (i.e MSI mapping, memory mapping) or 
> sanitizing when the configuration space is updated by the hardware 
> domain.
>
> Cheers,
>


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

  reply	other threads:[~2017-07-20 11:00 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-26 17:14 [RFC] ARM PCI Passthrough design document Julien Grall
2017-05-29  2:30 ` Manish Jaggi
2017-05-29 18:14   ` Julien Grall
2017-05-30  5:53     ` Manish Jaggi
2017-05-30  9:33       ` Julien Grall
2017-05-30  7:53     ` Roger Pau Monné
2017-05-30  9:42       ` Julien Grall
2017-05-30  7:40 ` Roger Pau Monné
2017-05-30  9:54   ` Julien Grall
2017-06-16  0:31     ` Stefano Stabellini
2017-06-16  0:23 ` Stefano Stabellini
2017-06-20  0:19 ` Vikram Sethi
2017-06-28 15:22   ` Julien Grall
2017-06-29 15:17     ` Vikram Sethi
2017-07-03 14:35       ` Julien Grall
2017-07-04  8:30     ` roger.pau
2017-07-06 20:55       ` Vikram Sethi
2017-07-07  8:49         ` Roger Pau Monné
2017-07-07 21:50           ` Stefano Stabellini
2017-07-07 23:40             ` Vikram Sethi
2017-07-08  7:34             ` Roger Pau Monné
2018-01-19 10:34               ` Manish Jaggi
2017-07-19 14:41 ` Notes from PCI Passthrough design discussion at Xen Summit Punit Agrawal
2017-07-20  3:54   ` Manish Jaggi
2017-07-20  8:24     ` Roger Pau Monné
2017-07-20  9:32       ` Manish Jaggi
2017-07-20 10:29         ` Roger Pau Monné
2017-07-20 10:47           ` Julien Grall
2017-07-20 11:06             ` Roger Pau Monné
2017-07-20 11:52               ` Julien Grall
2017-07-20 11:02           ` Manish Jaggi
2017-07-20 10:41         ` Julien Grall
2017-07-20 11:00           ` Manish Jaggi [this message]
2017-07-20 12:24             ` Julien Grall
2018-01-22 11:10 ` [RFC] ARM PCI Passthrough design document Manish Jaggi

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=b8113dbf-e01e-1834-366c-53376a23e0be@caviumnetworks.com \
    --to=mjaggi@caviumnetworks.com \
    --cc=Dave.Martin@arm.com \
    --cc=JBeulich@suse.com \
    --cc=Steve.Capper@arm.com \
    --cc=Vijaya.Kumar@caviumnetworks.com \
    --cc=Wei.Chen@arm.com \
    --cc=andre.przywara@arm.com \
    --cc=edgar.iglesias@xilinx.com \
    --cc=julien.grall@linaro.org \
    --cc=manish.jaggi@caviumnetworks.com \
    --cc=okaya@qti.qualcomm.com \
    --cc=punit.agrawal@arm.com \
    --cc=roger.pau@citrix.com \
    --cc=sgoel@qti.qualcomm.com \
    --cc=sstabellini@kernel.org \
    --cc=vikrams@qti.qualcomm.com \
    --cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.