From: "Cédric Le Goater" <clg@redhat.com>
To: Rorie Reyes <rreyes@linux.ibm.com>,
qemu-devel@nongnu.org, qemu-s390x@nongnu.org
Cc: pbonzini@redhat.com, cohuck@redhat.com, pasic@linux.ibm.com,
jjherne@linux.ibm.com, borntraeger@linux.ibm.com,
alex.williamson@redhat.com, thuth@redhat.com,
akrowiak@linux.ibm.com
Subject: Re: [RFC PATCH v9 2/4] hw/vfio/ap: store object indicating AP config changed in a queue
Date: Thu, 22 May 2025 17:36:29 +0200 [thread overview]
Message-ID: <73d159e9-abde-4f97-8d04-4f8f8783975d@redhat.com> (raw)
In-Reply-To: <38ba5741-e564-4812-87e2-ba6235e077b1@linux.ibm.com>
On 5/22/25 16:28, Rorie Reyes wrote:
>
> On 5/22/25 9:27 AM, Cédric Le Goater wrote:
>> On 5/12/25 20:02, Rorie Reyes wrote:
>>> Creates an object indicating that an AP configuration change event
>>> has been received and stores it in a queue. These objects will later
>>> be used to store event information for an AP configuration change
>>> when the CHSC instruction is intercepted.
>>>
>>> Signed-off-by: Rorie Reyes <rreyes@linux.ibm.com>
>>> ---
>>> hw/vfio/ap.c | 12 ++++++++++++
>>> 1 file changed, 12 insertions(+)
>>>
>>> diff --git a/hw/vfio/ap.c b/hw/vfio/ap.c
>>> index 3d0af7a54a..5ea5dd9cca 100644
>>> --- a/hw/vfio/ap.c
>>> +++ b/hw/vfio/ap.c
>>> @@ -41,6 +41,13 @@ struct VFIOAPDevice {
>>> EventNotifier cfg_notifier;
>>> };
>>> +typedef struct APConfigChgEvent {
>>> + QTAILQ_ENTRY(APConfigChgEvent) next;
>>> +} APConfigChgEvent;
>>> +
>>> +QTAILQ_HEAD(, APConfigChgEvent) cfg_chg_events =
>>> + QTAILQ_HEAD_INITIALIZER(cfg_chg_events);
>>> +
>>
>> Could cfg_chg_events be static ?
>>
>>
>> Thanks,
>>
>> C.
>>
> You make a good point, Cedric. I'm only using this variable in ap.c. Having it as a static would prevent it from being modified anywhere else
>
Good. Would you have time to send a v10 ?
Thanks,
C.
next prev parent reply other threads:[~2025-05-22 15:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 18:02 [RFC PATCH v9 0/4] Report vfio-ap configuration changes Rorie Reyes
2025-05-12 18:02 ` [RFC PATCH v9 1/4] hw/vfio/ap: notification handler for AP config changed event Rorie Reyes
2025-05-12 18:02 ` [RFC PATCH v9 2/4] hw/vfio/ap: store object indicating AP config changed in a queue Rorie Reyes
2025-05-13 11:38 ` Anthony Krowiak
2025-05-22 13:27 ` Cédric Le Goater
2025-05-22 14:28 ` Rorie Reyes
2025-05-22 15:36 ` Cédric Le Goater [this message]
2025-05-22 15:55 ` Rorie Reyes
2025-05-23 2:30 ` Rorie Reyes
2025-05-12 18:02 ` [RFC PATCH v9 3/4] hw/vfio/ap: Storing event information for an AP configuration change event Rorie Reyes
2025-05-13 11:38 ` Anthony Krowiak
2025-05-22 13:30 ` Cédric Le Goater
2025-05-22 17:17 ` Rorie Reyes
2025-05-22 19:05 ` Anthony Krowiak
2025-05-22 18:55 ` Anthony Krowiak
2025-05-26 8:43 ` Cédric Le Goater
2025-05-27 11:58 ` Anthony Krowiak
2025-05-22 13:35 ` Cédric Le Goater
2025-05-22 19:02 ` Anthony Krowiak
2025-05-23 3:05 ` Rorie Reyes
2025-05-23 3:27 ` Rorie Reyes
2025-05-12 18:02 ` [RFC PATCH v9 4/4] s390: implementing CHSC SEI for AP config change Rorie Reyes
2025-05-13 11:08 ` Cédric Le Goater
2025-05-13 11:38 ` Anthony Krowiak
2025-05-20 6:52 ` Cédric Le Goater
2025-05-20 13:17 ` Rorie Reyes
2025-05-13 11:47 ` [RFC PATCH v9 0/4] Report vfio-ap configuration changes Cédric Le Goater
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=73d159e9-abde-4f97-8d04-4f8f8783975d@redhat.com \
--to=clg@redhat.com \
--cc=akrowiak@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=borntraeger@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=jjherne@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rreyes@linux.ibm.com \
--cc=thuth@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;
as well as URLs for NNTP newsgroup(s).