From: "Cédric Le Goater" <clg@redhat.com>
To: Shivaprasad G Bhat <sbhat@linux.ibm.com>,
harshpb@linux.ibm.com, npiggin@gmail.com
Cc: danielhb413@gmail.com, david@gibson.dropbear.id.au,
alex.williamson@redhat.com, qemu-ppc@nongnu.org,
zhenzhong.duan@intel.com, qemu-devel@nongnu.org
Subject: Re: [PATCH] vfio: container: Fix missing allocation of VFIOSpaprContainer
Date: Fri, 28 Jun 2024 12:37:08 +0200 [thread overview]
Message-ID: <8ba04617-f18d-4c84-8bed-d3ddfa87d5b7@redhat.com> (raw)
In-Reply-To: <65126343-344e-47a0-bf63-7df43b0051ca@linux.ibm.com>
...
> Could you clarify which tree you are referring to ? I see his tree
>
> https://github.com/awilliam/tests is bit old and updated recently, however
>
> I have been using those tests for my unit testing.
Yes, this tree.
...
> This went through cycles of breakage and fixes. It worked on 5.18(not sure
>
> about older ones before that), and broke afterwards. Recently fixed
>
> and working from 6.4, broken on 6.7. Fixed and working in 6.8
>
> onwards now.
Good. It should be fixed in the next debian.
> Yes, TCG too works, missed to mention.
and a TCG guest under an intel host ? This used to work.
Thanks,
C.
next prev parent reply other threads:[~2024-06-28 10:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 19:14 [PATCH] vfio: container: Fix missing allocation of VFIOSpaprContainer Shivaprasad G Bhat
2024-05-10 2:34 ` Duan, Zhenzhong
2024-05-13 12:23 ` Cédric Le Goater
2024-05-22 16:15 ` Shivaprasad G Bhat
2024-05-27 13:35 ` Cédric Le Goater
2024-06-20 13:07 ` Cédric Le Goater
2024-06-21 8:17 ` Shivaprasad G Bhat
2024-06-21 8:49 ` Cédric Le Goater
2024-06-21 14:47 ` Shivaprasad G Bhat
2024-06-21 15:10 ` Cédric Le Goater
2024-06-26 3:56 ` Shivaprasad G Bhat
2024-06-28 10:37 ` Cédric Le Goater [this message]
2024-07-01 16:49 ` Shivaprasad G Bhat
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=8ba04617-f18d-4c84-8bed-d3ddfa87d5b7@redhat.com \
--to=clg@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=harshpb@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=sbhat@linux.ibm.com \
--cc=zhenzhong.duan@intel.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;
as well as URLs for NNTP newsgroup(s).