public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Thomas Huth <thuth@redhat.com>,
	Halil Pasic <pasic@linux.vnet.ibm.com>,
	Cornelia Huck <cohuck@redhat.com>
Cc: linux-s390@vger.kernel.org,
	virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
	kbuild-all@01.org, kbuild test robot <fengguang.wu@intel.com>
Subject: Re: [PATCH] virtio/s390: fixup for implement PM operations for virtio_ccw
Date: Mon, 18 Dec 2017 09:59:14 +0100	[thread overview]
Message-ID: <c5c804cd-bfba-e078-9ad4-6e9dea4c2404@de.ibm.com> (raw)
In-Reply-To: <88011e21-2a91-5d18-d5c9-384decac3b79@redhat.com>



On 12/18/2017 09:52 AM, Thomas Huth wrote:
> On 18.12.2017 09:37, Christian Borntraeger wrote:
>> We need to disable the pm callbacks if CONFIG_PM is not set.
>>
>> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
>> ---
>> Cornelia, you might want to squash this into the original commit.
>>
>>  drivers/s390/virtio/virtio_ccw.c | 4 ++++
>>  1 file changed, 4 insertions(+)
>>
>> diff --git a/drivers/s390/virtio/virtio_ccw.c b/drivers/s390/virtio/virtio_ccw.c
>> index 330b3fa3430a..985184ebda45 100644
>> --- a/drivers/s390/virtio/virtio_ccw.c
>> +++ b/drivers/s390/virtio/virtio_ccw.c
>> @@ -1315,6 +1315,7 @@ static struct ccw_device_id virtio_ids[] = {
>>  	{},
>>  };
>>  
>> +#ifdef CONFIG_PM_SLEEP
>>  static int virtio_ccw_freeze(struct ccw_device *cdev)
>>  {
>>  	struct virtio_ccw_device *vcdev = dev_get_drvdata(&cdev->dev);
>> @@ -1333,6 +1334,7 @@ static int virtio_ccw_restore(struct ccw_device *cdev)
>>  
>>  	return virtio_device_restore(&vcdev->vdev);
>>  }
>> +#endif
>>  
>>  static struct ccw_driver virtio_ccw_driver = {
>>  	.driver = {
>> @@ -1346,9 +1348,11 @@ static struct ccw_driver virtio_ccw_driver = {
>>  	.set_online = virtio_ccw_online,
>>  	.notify = virtio_ccw_cio_notify,
>>  	.int_class = IRQIO_VIR,
>> +#ifdef CONFIG_PM_SLEEP
>>  	.freeze = virtio_ccw_freeze,
>>  	.thaw = virtio_ccw_restore,
>>  	.restore = virtio_ccw_restore,
>> +#endif
>>  };
> 
> Some other drivers rather seem to test CONFIG_HIBERNATE_CALLBACKS ...
> would that be a more appropriate config flag here?

The virtio code uses CONFIG_PM_SLEEP (and we call that code). 

See
include/linux/virtio.h

c6716bae52f97 (Michael S. Tsirkin 2014-10-14 10:40:35 +1030 155) #ifdef CONFIG_PM_SLEEP
c6716bae52f97 (Michael S. Tsirkin 2014-10-14 10:40:35 +1030 156) int virtio_device_freeze(struct virtio_device *dev);
c6716bae52f97 (Michael S. Tsirkin 2014-10-14 10:40:35 +1030 157) int virtio_device_restore(struct virtio_device *dev);
c6716bae52f97 (Michael S. Tsirkin 2014-10-14 10:40:35 +1030 158) #endif



So I think CONFIG_PM_SLEEP is the best fit.

      reply	other threads:[~2017-12-18  8:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201712171200.w6OAf5Jm%fengguang.wu@intel.com>
2017-12-18  8:37 ` [PATCH] virtio/s390: fixup for implement PM operations for virtio_ccw Christian Borntraeger
2017-12-18  8:49   ` Cornelia Huck
2017-12-18  8:52   ` Thomas Huth
2017-12-18  8:59     ` Christian Borntraeger [this message]

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=c5c804cd-bfba-e078-9ad4-6e9dea4c2404@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=pasic@linux.vnet.ibm.com \
    --cc=thuth@redhat.com \
    --cc=virtualization@lists.linux-foundation.org \
    /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