From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Alex Williamson <alex.williamson@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH] pci-assign: Do not reset the device unless the kernel supports it
Date: Tue, 07 Jun 2011 11:06:53 +0300 [thread overview]
Message-ID: <4DEDDC1D.7000905@redhat.com> (raw)
In-Reply-To: <4DED4EDA.80803@web.de>
On 06/07/2011 01:04 AM, Jan Kiszka wrote:
> On 2011-06-06 23:48, Alex Williamson wrote:
> > On Mon, 2011-06-06 at 23:30 +0200, Jan Kiszka wrote:
> >> From: Jan Kiszka<jan.kiszka@siemens.com>
> >>
> >> At least kernels 2.6.38 and 2.6.39 do not properly support issuing a
> >> reset on an assigned device and corrupt its config space. Prevent
> >> this by checking for a host kernel with the required support, tagged by
> >> the to-be-introduced KVM_CAP_DEVICE_RESET.
> >
> > Wouldn't it be easier just to revert ed78661f in 2.6.39 stable? I guess
> > we don't have an option to do that for .38 since stable is done there,
> > but there are also some intel-iommu breakages that won't make stable for
> > that release. It seems like the userspace invoked reset resolves known,
> > demonstrable issues of devices continuing to DMA into guest memory while
> > ed78661f is mostly a theoretical change.
>
> Easier would be this patch. But I don't mind reverting the problematic
> commit in 39, whatever is preferred. We should just resolve the issue
> finally.
Kernel problems should be solved in the kernel (with exceptions of
course, but don't see the need here).
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2011-06-07 8:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 21:30 [PATCH] pci-assign: Do not reset the device unless the kernel supports it Jan Kiszka
2011-06-06 21:48 ` Alex Williamson
2011-06-06 22:04 ` Jan Kiszka
2011-06-07 8:06 ` Avi Kivity [this message]
2011-06-07 8:14 ` Jan Kiszka
2011-06-07 18:46 ` Alex Williamson
2011-06-08 7:52 ` Jan Kiszka
2011-06-09 8:10 ` Avi Kivity
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=4DEDDC1D.7000905@redhat.com \
--to=avi@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
/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