From: Avi Kivity <avi@redhat.com>
To: Jes Sorensen <jes@sgi.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Hollis Blanchard <hollisb@us.ibm.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"kvm-ia64@vger.kernel.org" <kvm-ia64@vger.kernel.org>,
Glauber de Oliveira Costa <glommer@gmail.com>
Subject: Re: [patch] remove vcpu_info array v5
Date: Tue, 04 Nov 2008 13:54:58 +0200 [thread overview]
Message-ID: <49103812.1070104@redhat.com> (raw)
In-Reply-To: <4909C00F.8050704@sgi.com>
Jes Sorensen wrote:
>
> So here we go, trying to catch up on the PCI passthrough patch revision
> number, here's v5 of the struct vcpu_info patch.
>
> In the end I decided to merge the contents of struct vcpu_info directly
> into CPU_COMMON as it was silly to create new files just to remove them
> in the next patch again.
>
> This boots for me on ia64 and builds on x86_64, obviously it is 100%
> perfect <tm>!
>
> Comments, bug reports, or upstream merge, welcome :-)
> Merge vcpu_info into CPUState.
>
> Move contents of struct vcpu_info directly into CPU_COMMON. Rename
> struct qemu_kvm_work_item to qemu_work_item as it really isn't KVM
> specific.
>
>
Well, it is actually kvm specific, since qemu doesn't have vccpu threads.
> -int kvm_run(kvm_context_t kvm, int vcpu)
> +int kvm_run(kvm_context_t kvm, int vcpu, void *env)
>
That's a little ugly -- passing two arguments which describe the vcpu.
How about passing env to kvm_create_vcpu() instead?
> #define CPU_TEMP_BUF_NLONGS 128
> #define CPU_COMMON \
> struct TranslationBlock *current_tb; /* currently executing TB */ \
> @@ -200,6 +204,15 @@
> /* user data */ \
> void *opaque; \
> \
> - const char *cpu_model_str;
> + const char *cpu_model_str; \
> + \
> + int sipi_needed; \
> + int init; \
> + pthread_t thread; \
> + int signalled; \
> + int stop; \
> + int stopped; \
> + int created; \
> + struct qemu_work_item *queued_work_first, *queued_work_last;
>
struct kvm_stuff { ... } and put that in as a member, so it's easier to
remember this is a kvm addition.
>
> #if defined(TARGET_I386) || defined(TARGET_X86_64)
> +#ifdef USE_KVM
> +static CPUState *qemu_kvm_cpu_env(int index)
> +{
> + CPUState *penv;
> +
> + penv = first_cpu;
> +
> + while (penv) {
> + if (penv->cpu_index == index)
> + return penv;
> + penv = (CPUState *)penv->next_cpu;
> + }
> +
> + return NULL;
> +}
> +#endif
>
This can't be the best way of determining the env pointer from a cpu number.
> @@ -143,4 +143,12 @@
> void cpu_save(QEMUFile *f, void *opaque);
> int cpu_load(QEMUFile *f, void *opaque, int version_id);
>
> +/* work queue */
> +struct qemu_work_item {
> + struct qemu_kvm_work_item *next;
>
Missed rename here.
> + void (*func)(void *data);
> + void *data;
> + int done;
> +};
> +
>
Please keep this in kvm specific files.
> @@ -28,7 +28,6 @@
> #include <sys/syscall.h>
> #include <sys/mman.h>
>
> -#define bool _Bool
>
why?
Please separate into a patch that does the kvm_run int vcpu -> void
*vcpu conversion, and then the vcpu_info -> env conversion.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-11-04 11:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 14:09 [patch] remove vcpu_info array v5 Jes Sorensen
2008-11-04 11:54 ` Avi Kivity [this message]
2008-11-04 13:55 ` Glauber Costa
2008-11-04 14:30 ` Avi Kivity
2008-11-04 14:35 ` Glauber Costa
2008-11-04 14:40 ` Avi Kivity
2008-11-04 14:43 ` Glauber Costa
2008-11-04 14:47 ` Avi Kivity
2008-11-10 13:30 ` Jes Sorensen
2008-11-10 13:40 ` Avi Kivity
2008-11-10 15:22 ` Anthony Liguori
2008-11-10 15:45 ` Avi Kivity
2008-11-10 15:47 ` Jes Sorensen
2008-11-10 15:54 ` Avi Kivity
2008-11-10 15:58 ` Jes Sorensen
2008-11-11 9:26 ` Avi Kivity
2008-11-12 13:02 ` Jes Sorensen
2008-11-12 13:09 ` Glauber Costa
2008-11-12 13:14 ` Avi Kivity
2008-11-12 13:12 ` Avi Kivity
2008-11-10 12:30 ` Jes Sorensen
2008-11-10 13:24 ` Jes Sorensen
2008-11-10 13:48 ` Avi Kivity
2008-11-13 16:46 ` [patch] pass opague CPUState through libkvm instead of int vcpu Jes Sorensen
2008-11-18 12:55 ` Avi Kivity
2008-11-18 12:59 ` Jes Sorensen
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=49103812.1070104@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=glommer@gmail.com \
--cc=hollisb@us.ibm.com \
--cc=jes@sgi.com \
--cc=kvm-ia64@vger.kernel.org \
--cc=kvm@vger.kernel.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