qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Desnogues <laurent.desnogues@gmail.com>
To: Glauber Costa <glommer@redhat.com>
Cc: Blue Swirl <blauwirbel@gmail.com>,
	aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] v3: don't call reset functions on cpu initialization
Date: Fri, 6 Nov 2009 19:43:48 +0100	[thread overview]
Message-ID: <761ea48b0911061043i5dbaaab5td2e0d34cc4ed68a9@mail.gmail.com> (raw)
In-Reply-To: <20091106181153.GB12533@mothafucka.localdomain>

On Fri, Nov 6, 2009 at 7:11 PM, Glauber Costa <glommer@redhat.com> wrote:
> On Fri, Nov 06, 2009 at 08:05:40PM +0200, Blue Swirl wrote:
>> On Thu, Nov 5, 2009 at 6:05 PM, Glauber Costa <glommer@redhat.com> wrote:
[...]
>> > --- a/target-i386/helper.c
>> > +++ b/target-i386/helper.c
>> > @@ -1885,7 +1885,9 @@ CPUX86State *cpu_x86_init(const char *cpu_model)
>> >         return NULL;
>> >     }
>> >     mce_init(env);
>> > +#ifdef CONFIG_USER_ONLY
>> >     cpu_reset(env);
>> > +#endif
>>
>> Please push the call to *-user/main.c, just after call to cpu_init().
> I'd prefer it that way too. But cpu_reset is also called in some other places,
> and Laurent suggested me to to this way.

Yes, you'd have to remove all calls to cpu_reset from all CPUs.
And also add a call to cpu_reset to cpu_copy.

> I don't really know much about -user, so I'm fine with whatever you guys agree on.

I honestly don't care that much as long as all targets still work
in user mode :-)

The aim was to make Glauber's patch less intrusive.


Laurent

  reply	other threads:[~2009-11-06 18:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-05 16:05 [Qemu-devel] [PATCH] v3: don't call reset functions on cpu initialization Glauber Costa
2009-11-06 18:05 ` Blue Swirl
2009-11-06 18:11   ` Glauber Costa
2009-11-06 18:43     ` Laurent Desnogues [this message]
2009-11-06 19:01       ` Blue Swirl
2009-11-06 19:13         ` Laurent Desnogues
2009-11-06 19:36           ` Blue Swirl
2009-11-06 19:50             ` Laurent Desnogues
2009-11-06 19:54               ` Blue Swirl
2009-11-06 20:41         ` Glauber Costa
2009-11-07  8:40           ` Blue Swirl
2009-11-07 16:02             ` Laurent Desnogues
2009-11-07 16:11               ` Blue Swirl
2009-11-07 16:15                 ` Laurent Desnogues

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=761ea48b0911061043i5dbaaab5td2e0d34cc4ed68a9@mail.gmail.com \
    --to=laurent.desnogues@gmail.com \
    --cc=aliguori@us.ibm.com \
    --cc=blauwirbel@gmail.com \
    --cc=glommer@redhat.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).