From: Rorie Reyes <rreyes@linux.ibm.com>
To: Thomas Huth <thuth@redhat.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, clg@redhat.com,
akrowiak@linux.ibm.com
Subject: Re: [RFC PATCH v4 5/5] s390: implementing CHSC SEI for AP config change
Date: Mon, 14 Apr 2025 10:57:01 -0400 [thread overview]
Message-ID: <1ba623ee-187a-4713-9ebc-6e491efba1c7@linux.ibm.com> (raw)
In-Reply-To: <9ee2d05c-cb62-4685-88b0-7f2f6ea2a006@redhat.com>
On 4/14/25 10:54 AM, Thomas Huth wrote:
> On 14/04/2025 16.37, Rorie Reyes wrote:
>> On 4/11/25 2:45 AM, Thomas Huth wrote:
>>
>>> #include CONFIG_DEVICES
>>>
>>> at the beginning of the ioinst.c file. Then you should be able to do:
>>>
>>> #ifdef CONFIG_VFIO_AP
>>> if (s390_has_feat(S390_FEAT_AP)) {
>>> return ap_chsc_sei_nt0_get_event(res);
>>> }
>>> #endif
>> This worked
>>>
>>> (or whatever the code should look like).
>>>
>>> Alternatively, and this might even be the nicer variant, add a file
>>> hw/ vfio/ap-stub.c and include a dummy ap_chsc_sei_nt0_get_event()
>>> function there. Then in hw/vfio/meson.build add this line:
>>>
>>> vfio_ss.add(when: 'CONFIG_VFIO_AP', if_false: files('ap-stub.c'))
>> This worked as well. Since you mentioned that this is a nicer
>> variant, I'll go with this change. What do you recommend I do for my
>> patches? Should I do an interactive rebase to add the new file
>> hw/vfio/ap-stub.c and updating hw/ vfio/meson.build? Or should I make
>> two new commits for each file (ap-stub.c and meson.build)
>
> Please do a "git rebase -i ..." to fix up the corresponding patch
> (that's what we're doing in the QEMU development workflow).
>
> Thanks
> Thomas
>
Thank you. I'll make those changes and send my patches later today
next prev parent reply other threads:[~2025-04-14 14:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 15:16 [RFC PATCH v4 0/5] Report vfio-ap configuration changes Rorie Reyes
2025-03-11 15:16 ` [RFC PATCH v4 1/5] linux-headers: NOTFORMERGE - placeholder uapi updates for AP config change Rorie Reyes
2025-03-11 15:16 ` [RFC PATCH v4 2/5] hw/vfio/ap: notification handler for AP config changed event Rorie Reyes
2025-03-11 15:16 ` [RFC PATCH v4 3/5] hw/vfio/ap: store object indicating AP config changed in a queue Rorie Reyes
2025-03-12 11:24 ` Anthony Krowiak
2025-03-11 15:16 ` [RFC PATCH v4 4/5] hw/vfio/ap: Storing event information for an AP configuration change event Rorie Reyes
2025-03-12 13:14 ` Anthony Krowiak
2025-03-11 15:16 ` [RFC PATCH v4 5/5] s390: implementing CHSC SEI for AP config change Rorie Reyes
2025-03-17 13:41 ` Thomas Huth
2025-03-25 13:47 ` Rorie Reyes
2025-04-10 20:31 ` Rorie Reyes
2025-04-11 6:45 ` Thomas Huth
2025-04-14 14:37 ` Rorie Reyes
2025-04-14 14:54 ` Thomas Huth
2025-04-14 14:57 ` Rorie Reyes [this message]
2025-03-12 13:48 ` [RFC PATCH v4 0/5] 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=1ba623ee-187a-4713-9ebc-6e491efba1c7@linux.ibm.com \
--to=rreyes@linux.ibm.com \
--cc=akrowiak@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=borntraeger@linux.ibm.com \
--cc=clg@redhat.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=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).