From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Michael Mueller <mimu@linux.ibm.com>, Yury Norov <yury.norov@gmail.com>
Cc: Claudio Imbrenda <imbrenda@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
kvm@vger.kernel.org, linux-s390@vger.kernel.org,
linux-kernel@vger.kernel.org,
Janosch Frank <frankja@linux.ibm.com>,
David Hildenbrand <david@redhat.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>
Subject: Re: [PATCH v1 1/1] KVM: s390: Don't cast parameter in bit operations
Date: Wed, 2 Mar 2022 17:44:03 +0200 [thread overview]
Message-ID: <Yh+Qw6Pb+Cd9JDNa@smile.fi.intel.com> (raw)
In-Reply-To: <3640a910-60fe-0935-4dfc-55bb65a75ce5@linux.ibm.com>
On Thu, Feb 24, 2022 at 01:10:34PM +0100, Michael Mueller wrote:
> On 24.02.22 12:36, Claudio Imbrenda wrote:
...
> we do that at several places
Thanks for pointing out.
> arch/s390/kernel/processor.c: for_each_set_bit_inv(bit, (long
> *)&stfle_fac_list, MAX_FACILITY_BIT)
This one requires a separate change, not related to this patch.
> arch/s390/kvm/interrupt.c: set_bit_inv(IPM_BIT_OFFSET + gisc, (unsigned long
> *) gisa);
This is done in the patch. Not sure how it appears in your list.
> arch/s390/kvm/kvm-s390.c: set_bit_inv(vcpu->vcpu_id, (unsigned long *)
> sca->mcn);
> arch/s390/kvm/kvm-s390.c: set_bit_inv(vcpu->vcpu_id, (unsigned long *)
> &sca->mcn);
These two should be fixed in a separate change.
Also this kind of stuff:
bitmap_copy(kvm->arch.cpu_feat, (unsigned long *) data.feat,
KVM_S390_VM_CPU_FEAT_NR_BITS);
might require a new API like
bitmap_from_u64_array()
bitmap_to_u64_array()
Yury?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-03-02 15:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 16:44 [PATCH v1 1/1] KVM: s390: Don't cast parameter in bit operations Andy Shevchenko
2022-02-24 11:36 ` Claudio Imbrenda
2022-02-24 12:10 ` Michael Mueller
2022-03-02 15:44 ` Andy Shevchenko [this message]
2022-03-02 17:18 ` Yury Norov
2022-03-02 17:31 ` Andy Shevchenko
2022-03-02 18:43 ` Yury Norov
2022-03-03 10:19 ` Andy Shevchenko
2022-02-24 19:51 ` Andy Shevchenko
2022-02-24 23:15 ` David Laight
2022-03-02 15:45 ` Andy Shevchenko
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=Yh+Qw6Pb+Cd9JDNa@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mimu@linux.ibm.com \
--cc=svens@linux.ibm.com \
--cc=yury.norov@gmail.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