From: Avi Kivity <avi@qumranet.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>,
Dor Laor <dor.laor@gmail.com>,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH 2/2] virtio reset support
Date: Tue, 29 Jan 2008 19:27:02 +0200 [thread overview]
Message-ID: <479F61E6.4010600@qumranet.com> (raw)
In-Reply-To: <479E5B9B.4070409@us.ibm.com>
Anthony Liguori wrote:
> Avi Kivity wrote:
>> Anthony Liguori wrote:
>>>
>>> PCI-e has a common reset concept (warm and cold). I've been looking
>>> around and I can't seem to find any common reset mechanism for PCI.
>>> Is FLR something that is per-device or a standard PCI mechanism? If
>>> it's the former, than we've basically implemented FLR using this bit
>>> in the config space.
>>>
>>
>> I believe it is a standard mechanism, albeit new, so perhaps many
>> devices don't implement it.
>
> I don't have a copy of the PCI specification handy. Can you dig up
> how it's implemented? I don't see any references in my local
> documentation and I couldn't find anything in Linux that referenced it
> at the PCI level.
>
I think it's NDA material, so even if I found it, I couldn't publish
it. It can probably be reverse-engineered from the Xen patches, or
perhaps your employer is a PCI-SIG member so you can get access to it.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2008-01-29 17:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 14:16 [PATCH 1/2] reset support: make net driver alloc/cleanup in probe and remove Rusty Russell
[not found] ` <200801240116.26160.rusty-8n+1lVoiYb80n/F98K4Iww@public.gmane.org>
2008-01-23 14:18 ` [PATCH 2/2] virtio reset support Rusty Russell
[not found] ` <200801240118.09032.rusty-8n+1lVoiYb80n/F98K4Iww@public.gmane.org>
2008-01-24 13:09 ` Dor Laor
[not found] ` <1201180147.7100.35.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-01-24 21:19 ` Rusty Russell
2008-01-27 13:22 ` Avi Kivity
[not found] ` <479C8599.60007-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-28 15:40 ` Anthony Liguori
[not found] ` <479DF787.2020100-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-01-28 15:48 ` Avi Kivity
[not found] ` <479DF952.9040201-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-28 22:47 ` Anthony Liguori
2008-01-29 17:27 ` Avi Kivity [this message]
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=479F61E6.4010600@qumranet.com \
--to=avi@qumranet.com \
--cc=aliguori@us.ibm.com \
--cc=dor.laor@gmail.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=virtualization@lists.linux-foundation.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