All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 43339] Wrong Pci-Bridge Header Type check.
Date: Tue,  5 Jun 2012 18:33:47 +0000 (UTC)	[thread overview]
Message-ID: <20120605183347.196AF11FC41@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-43339-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=43339


Alex Williamson <alex.williamson@redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |alex.williamson@redhat.com




--- Comment #1 from Alex Williamson <alex.williamson@redhat.com>  2012-06-05 18:33:46 ---
(In reply to comment #0)
> 
> So, 1 & 0xE == 0 thus KVM assigns pci-bridge device to VM successfully.

Have you found this to be true in practice?  The test here is clearly wrong,
but immediately after this we test pci-sysfs resource permissions.  We only
test standard device resources, as we're not expecting a bridge to get through,
but I believe those should all be zero for a bridge, which will result in
denying assignment of the device because it has no resources.  If you have a
pci-bridge that actually makes it through that test, please include lspci -vvv
for it here.  Thanks

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  reply	other threads:[~2012-06-05 18:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-04 14:28 [Bug 43339] New: Wrong Pci-Bridge Header Type check bugzilla-daemon
2012-06-05 18:33 ` bugzilla-daemon [this message]
2012-06-05 19:43 ` [Bug 43339] " bugzilla-daemon
2012-07-01  9:40 ` bugzilla-daemon
2012-08-15 22:00 ` bugzilla-daemon

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=20120605183347.196AF11FC41@bugzilla.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kvm@vger.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 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.