All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
	Cornelia Huck <cohuck@redhat.com>
Cc: Richard Henderson <rth@twiddle.net>,
	Alexander Graf <agraf@suse.de>,
	Yi Min Zhao <zyimin@linux.vnet.ibm.com>,
	Halil Pasic <pasic@linux.vnet.ibm.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	"Jason J . Herne" <jjherne@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v2 1/2] s390x/ais: enable ais when migration is available
Date: Tue, 26 Sep 2017 16:08:05 +0200	[thread overview]
Message-ID: <5a6075ac-cbf7-cd2b-bdfa-e3f19cbf2a5b@redhat.com> (raw)
In-Reply-To: <debb11b6-3eba-b2fe-961f-52df7b1c5926@de.ibm.com>

On 26.09.2017 16:06, Christian Borntraeger wrote:
> 
> 
> On 09/26/2017 03:43 PM, David Hildenbrand wrote:
>>
>>> +    /* try enable the AIS facility */
>>> +    test_attr.group = KVM_DEV_FLIC_AISM_ALL;
>>> +    if (!ioctl(flic_state->fd, KVM_HAS_DEVICE_ATTR, test_attr)) {
>>> +            kvm_vm_enable_cap(kvm_state, KVM_CAP_S390_AIS, 0);
>>> +    }
>>> +
>>>      return;
>>>  fail:
>>>      error_propagate(errp, errp_local);
>>> @@ -578,7 +584,7 @@ static void kvm_s390_flic_reset(DeviceState *dev)
>>>  
>>>      flic_disable_wait_pfault(flic);
>>>  
>>> -    if (fs->ais_supported) {
>>> +    if (s390_has_feat(S390_FEAT_ADAPTER_INT_SUPPRESSION)) {
>>
>> I don't remember if a reset is trigger on realization. Most probably
>> not, but it could be.
>>
>> Would it hurt if the following code would not get called if the flic
>> hasn't been used yet? (possible reset before cpu model has been
>> initialized) - are kvm_s390_modify_ais_mode() calls required before ais
>> can be used for the first time?
> 
> Hmm, simm/nimm should default to zero in the kernel I guess. So I think it would
> not hurt. Yi Min, correct?
> 
> 
> Anyway it seems that reset is NOT called during realize, the first
> call is
> 
>                 #0  0x00000000010e5178 kvm_s390_flic_reset (qemu-system-s390x)
>                 #1  0x000000000124bbc4 device_reset (qemu-system-s390x)
>                 #2  0x0000000001248cd0 qdev_reset_one (qemu-system-s390x)
>                 #3  0x0000000001249ea4 qdev_walk_children (qemu-system-s390x)
>                 #4  0x000000000124fd3a qbus_walk_children (qemu-system-s390x)
>                 #5  0x0000000001248e6c qbus_reset_all (qemu-system-s390x)
>                 #6  0x0000000001248eae qbus_reset_all_fn (qemu-system-s390x)
>                 #7  0x0000000001250a60 qemu_devices_reset (qemu-system-s390x)
>                 #8  0x0000000001143c80 s390_machine_reset (qemu-system-s390x)
>                 #9  0x00000000011c5b72 qemu_system_reset (qemu-system-s390x)
>                 #10 0x00000000011ceb8e main (qemu-system-s390x)
>                 #11 0x000003ff947a289a __libc_start_main (libc.so.6)
>                 #12 0x0000000001017646 _start (qemu-system-s390x)
> 
> 

Reviewed-by: David Hildenbrand <david@redhat.com>

than

-- 

Thanks,

David

  reply	other threads:[~2017-09-26 14:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-26 13:36 [Qemu-devel] [PATCH v2 0/2] ais fixups for 2.11 Christian Borntraeger
2017-09-26 13:36 ` [Qemu-devel] [PATCH v2 1/2] s390x/ais: enable ais when migration is available Christian Borntraeger
2017-09-26 13:43   ` David Hildenbrand
2017-09-26 14:06     ` Christian Borntraeger
2017-09-26 14:08       ` David Hildenbrand [this message]
2017-09-27  4:35       ` Yi Min Zhao
2017-09-27  5:45   ` Yi Min Zhao
2017-09-27  7:02     ` Christian Borntraeger
2017-09-26 13:36 ` [Qemu-devel] [PATCH v2 2/2] s390x/ais: disable ais for compat machines Christian Borntraeger
2017-09-26 13:51   ` David Hildenbrand
2017-09-27  7:12     ` Christian Borntraeger
2017-09-27  8:03       ` Christian Borntraeger

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=5a6075ac-cbf7-cd2b-bdfa-e3f19cbf2a5b@redhat.com \
    --to=david@redhat.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=jjherne@linux.vnet.ibm.com \
    --cc=pasic@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=zyimin@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.