The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Cal Peake <cp@absolutedigital.net>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Vishal Annapurve <vannapurve@google.com>,
	"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	Alex Williamson <alex.williamson@redhat.com>
Subject: Re: [STABLE] 6.12.23: vfio error (was: arch/x86/coco/tdx/tdx.c build error)
Date: Thu, 17 Apr 2025 16:37:50 +0200	[thread overview]
Message-ID: <2025041738-rocklike-undergrad-14d6@gregkh> (raw)
In-Reply-To: <66f3e1b3-6165-4a2e-f34c-de6fef86e441@absolutedigital.net>

On Mon, Apr 14, 2025 at 07:55:06PM -0400, Cal Peake wrote:
> On Sun, 13 Apr 2025, Cal Peake wrote:
> 
> > After booting the new kernel, I get errors trying to do vfio passthrough:
> > 
> > qemu-8.2-system-x86_64: vfio: Cannot reset device 0000:14:00.3, no available reset mechanism.
> > qemu-8.2-system-x86_64: vfio: Cannot reset device 0000:14:00.2, no available reset mechanism.
> > qemu-8.2-system-x86_64: vfio: Cannot reset device 0000:14:00.1, no available reset mechanism.
> > qemu-8.2-system-x86_64: vfio: Cannot reset device 0000:14:00.0, no available reset mechanism.
> 
> This was resolved by Alex Williamson, with his patch:
> 
> https://lore.kernel.org/lkml/20250414211828.3530741-1-alex.williamson@redhat.com/

Is this in Linus's tree yet?

thanks,

greg k-h

  reply	other threads:[~2025-04-17 14:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-12 20:48 [PATCH] [STABLE] 6.12.23: arch/x86/coco/tdx/tdx.c build error Cal Peake
2025-04-13 23:55 ` [STABLE] 6.12.23: vfio error (was: arch/x86/coco/tdx/tdx.c build error) Cal Peake
2025-04-14 23:55   ` Cal Peake
2025-04-17 14:37     ` Greg Kroah-Hartman [this message]
2025-04-17 19:00       ` Cal Peake

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=2025041738-rocklike-undergrad-14d6@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=alex.williamson@redhat.com \
    --cc=cp@absolutedigital.net \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vannapurve@google.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