public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: Prasad Joshi <P.G.Joshi@student.reading.ac.uk>
Cc: Chris Wright <chrisw@sous-sol.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	Tejun Heo <tj@kernel.org>
Subject: Re: Query on IOMMU
Date: Tue, 21 Dec 2010 12:01:44 -0800	[thread overview]
Message-ID: <20101221200144.GI15023@sequoia.sous-sol.org> (raw)
In-Reply-To: <000DF292CEBFBB41A633359D615F1514022A6020@DB2PRD0103MB011.eurprd01.prod.exchangelabs.com>

* Prasad Joshi (P.G.Joshi@student.reading.ac.uk) wrote:
> > From: Chris Wright [chrisw@sous-sol.org]
> > Sent: 21 December 2010 19:29
> > To: Prasad Joshi
> > Cc: Chris Wright; kvm@vger.kernel.org; Tejun Heo
> > Subject: Re: Query on IOMMU
> 
> > * Prasad Joshi (P.G.Joshi@student.reading.ac.uk) wrote:
> >> Besides when I insert the pci_stub module, it emits a messages
> >> [   49.197112] pci-stub: invalid id string ""
> >> I don't know why?
> 
> > It's just broken error message.  The commit b439b1d ("PCI: pci-stub: add
> > pci_stub.ids parameter") created that.  I looked at it very briefly a few
> > weeks ago and didn't see the issue.  It's cosmetic, and not related to
> > the failure you are seeing.
> 
> Is it okay to add a following line in section 4. unbind device from host kernel driver (example PCI device 01:00.0)
> 
> * If the PCI Stub Driver is compiled as module, then load the module using modprobe pci_stub.
> 
> When I compiled the kernel I selected it as a kernel module. As the driver was not loaded, I could not see the entries in /sys file system. I could figure that out after reading few things. It will good to add a note to mention this fact.
> 
> Let me know if I should add it or not.

Yes, that sounds fine.

thanks,
-chris

  reply	other threads:[~2010-12-21 20:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-21 16:00 Query on IOMMU Prasad Joshi
2010-12-21 16:15 ` Chris Wright
2010-12-21 16:54   ` Prasad Joshi
2010-12-21 17:12     ` Chris Wright
2010-12-21 17:39       ` Prasad Joshi
2010-12-21 18:33         ` Chris Wright
     [not found]           ` <000DF292CEBFBB41A633359D615F1514022A5FF4@DB2PRD0103MB011.eurprd01.prod.exchangelabs.com>
2010-12-21 19:22             ` Prasad Joshi
2010-12-21 19:29               ` Chris Wright
2010-12-21 19:56                 ` Prasad Joshi
2010-12-21 20:01                   ` Chris Wright [this message]
2010-12-21 20:06                     ` Prasad Joshi
2010-12-22  9:06                 ` [PATCH] pci-stub: ignore zero-length id parameters Tejun Heo
2010-12-23 20:54                   ` Jesse Barnes
2010-12-21 20:34             ` Query on IOMMU Chris Wright
2010-12-22 13:16               ` Prasad Joshi
2010-12-22 13:35                 ` Prasad Joshi
2010-12-22 14:56                   ` Chris Wright
2010-12-22 14:54                 ` Chris Wright
2010-12-22 15:02                   ` Prasad Joshi
2010-12-22 15:22                     ` Chris Wright
2010-12-22 15:46                       ` Prasad Joshi
2010-12-22 16:34                         ` Prasad Joshi

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=20101221200144.GI15023@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=P.G.Joshi@student.reading.ac.uk \
    --cc=kvm@vger.kernel.org \
    --cc=tj@kernel.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