From: Michael Mueller <mimu@linux.vnet.ibm.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: linux-s390@vger.kernel.org, Eduardo Habkost <ehabkost@redhat.com>,
kvm@vger.kernel.org, Gleb Natapov <gleb@kernel.org>,
linux-kernel@vger.kernel.org, qemu-devel@nongnu.org,
Christian Borntraeger <borntraeger@de.ibm.com>,
Alexander Graf <agraf@suse.de>,
"Jason J. Herne" <jjherne@linux.vnet.ibm.com>,
Daniel Hansel <daniel.hansel@linux.vnet.ibm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Andreas Faerber <afaerber@suse.de>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v5 11/17] target-s390x: Add KVM VM attribute interface for S390 CPU models
Date: Mon, 27 Apr 2015 15:01:30 +0200 [thread overview]
Message-ID: <20150427150130.134689ab@bee> (raw)
In-Reply-To: <20150427141913.7014b017.cornelia.huck@de.ibm.com>
On Mon, 27 Apr 2015 14:19:13 +0200
Cornelia Huck <cornelia.huck@de.ibm.com> wrote:
> > > >> Would it make sense to do the cast here....
> > > >
> > > > cpu_model_get/set() is used to handle both attributes,
> > > > KVM_S390_VM_CPU_MACHINE and KVM_S390_VM_CPU_PROCESSOR.
> > > > Both require a different type in the signature, (S390ProcessorProps*)
> > > > and (S390MachineProps*). Adding both as parameters seems to be odd
> > > > and would require additionally logic in the function.
> > > > Thus I think doing the cast outside is just the right thing to do.
> > >
> > > So what about a void pointer then as parameter?
> > > I prefer a pointer for qemu process memory over uint64_t as part of the
> > > function interface. This makes it somewhat clearer that this is an
> > > address within QEMU. Both ways will certainly work, though.
> >
> > The interface calls are:
> >
> > int kvm_s390_get_machine_props(KVMState *s, S390MachineProps *prop)
> > int kvm_s390_get_processor_props(S390ProcessorProps *prop)
> >
> > cpu_model_get/set() are just static helpers.
>
> So this makes them internal calls...
>
> >
> > >
> > > Conny, I guess you will pick up the patches. Any preference?
>
> ...and I'd prefer using a void pointer for them.
Ok, I will make void pointers then to emphasize their address characteristics.
Michael
next prev parent reply other threads:[~2015-04-27 13:01 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 13:56 [Qemu-devel] [PATCH v5 00/17] s390x cpu model implementation Michael Mueller
2015-04-13 13:56 ` [Qemu-devel] [PATCH v5 01/17] Introduce stub routine cpu_desc_avail Michael Mueller
2015-04-13 13:56 ` [Qemu-devel] [PATCH v5 02/17] Add accelerator id and model name to CPUState Michael Mueller
2015-04-13 13:56 ` [Qemu-devel] [PATCH v5 03/17] Extend QMP command query-cpus to return accelerator id and model name Michael Mueller
2015-04-13 13:56 ` [Qemu-devel] [PATCH v5 04/17] Extend HMP command info cpus to display " Michael Mueller
2015-04-13 13:56 ` [Qemu-devel] [PATCH v5 05/17] Add optional parameters to QMP command query-cpu-definitions Michael Mueller
2015-04-13 13:56 ` [Qemu-devel] [PATCH v5 06/17] target-s390x: Introduce S390 CPU facilities Michael Mueller
2015-04-27 8:11 ` Christian Borntraeger
2015-04-27 8:55 ` Michael Mueller
2015-04-27 10:14 ` Christian Borntraeger
2015-04-27 10:32 ` Michael Mueller
2015-04-13 13:56 ` [Qemu-devel] [PATCH v5 07/17] target-s390x: Generate facility defines per S390 CPU model Michael Mueller
2015-04-13 13:56 ` [Qemu-devel] [PATCH v5 08/17] target-s390x: Introduce S390 CPU models Michael Mueller
2015-04-13 13:56 ` [Qemu-devel] [PATCH v5 09/17] target-s390x: Define S390 CPU model specific facility lists Michael Mueller
2015-04-27 8:11 ` Christian Borntraeger
2015-04-27 8:59 ` Michael Mueller
2015-04-13 13:56 ` [Qemu-devel] [PATCH v5 10/17] target-s390x: Add S390 CPU model alias definition routines Michael Mueller
2015-04-27 8:11 ` Christian Borntraeger
2015-04-13 13:56 ` [Qemu-devel] [PATCH v5 11/17] target-s390x: Add KVM VM attribute interface for S390 CPU models Michael Mueller
2015-04-27 8:15 ` Christian Borntraeger
2015-04-27 9:43 ` Michael Mueller
2015-04-27 10:52 ` Christian Borntraeger
2015-04-27 11:07 ` Michael Mueller
2015-04-27 12:19 ` Cornelia Huck
2015-04-27 13:01 ` Michael Mueller [this message]
2015-04-13 13:56 ` [Qemu-devel] [PATCH v5 12/17] target-s390x: Add S390 CPU class initialization routines Michael Mueller
2015-04-13 13:56 ` [Qemu-devel] [PATCH v5 13/17] target-s390x: Prepare accelerator during S390 CPU object realization Michael Mueller
2015-04-13 13:56 ` [Qemu-devel] [PATCH v5 14/17] target-s390x: Initialize S390 CPU model name in CPUState Michael Mueller
2015-04-13 13:56 ` [Qemu-devel] [PATCH v5 15/17] target-s390x: Extend arch specific QMP command query-cpu-definitions Michael Mueller
2015-04-27 8:11 ` Christian Borntraeger
2015-04-27 10:29 ` Michael Mueller
2015-04-13 13:56 ` [Qemu-devel] [PATCH v5 16/17] target-s390x: Introduce S390 CPU facility test routine Michael Mueller
2015-04-13 13:56 ` [Qemu-devel] [PATCH v5 17/17] target-s390x: Enable S390 CPU model usage Michael Mueller
2015-04-27 8:11 ` [Qemu-devel] [PATCH v5 00/17] s390x cpu model implementation 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=20150427150130.134689ab@bee \
--to=mimu@linux.vnet.ibm.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=daniel.hansel@linux.vnet.ibm.com \
--cc=ehabkost@redhat.com \
--cc=gleb@kernel.org \
--cc=jjherne@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).