[Qemu-devel] x86 AREG0 patches

[Qemu-devel] x86 AREG0 patches

[Blue Swirl]

Hi,

A preview of x86 AREG0 patches can be found at the usual place:
URL	git://repo.or.cz/qemu/blueswirl.git
	http://repo.or.cz/r/qemu/blueswirl.git

This is obviously 1.2 material.

Re: [Qemu-devel] x86 AREG0 patches

[陳韋任]

On Sun, May 13, 2012 at 09:04:39PM +0000, Blue Swirl wrote:
> Hi,
> 
> A preview of x86 AREG0 patches can be found at the usual place:
> URL	git://repo.or.cz/qemu/blueswirl.git
> 	http://repo.or.cz/r/qemu/blueswirl.git
> 
> This is obviously 1.2 material.

  Is this patch will remove AREG0 so that we can use clang to compile QEMU?
How much the performance lose?

Regards,
chenwj

-- 
Wei-Ren Chen (陳韋任)
Computer Systems Lab, Institute of Information Science,
Academia Sinica, Taiwan (R.O.C.)
Tel:886-2-2788-3799 #1667
Homepage: http://people.cs.nctu.edu.tw/~chenwj

Re: [Qemu-devel] x86 AREG0 patches

[Blue Swirl]

On Mon, May 14, 2012 at 10:10 AM, 陳韋任 <chenwj@iis.sinica.edu.tw> wrote:
> On Sun, May 13, 2012 at 09:04:39PM +0000, Blue Swirl wrote:
>> Hi,
>>
>> A preview of x86 AREG0 patches can be found at the usual place:
>> URL   git://repo.or.cz/qemu/blueswirl.git
>>       http://repo.or.cz/r/qemu/blueswirl.git
>>
>> This is obviously 1.2 material.
>
>  Is this patch will remove AREG0 so that we can use clang to compile QEMU?

That should be possible eventually. I have only used clang analyzer,
not the compiler. Besides AREG0 (register variables), other GCC
extensions like variable length arrays need fixing but that should be
trivial.

> How much the performance lose?

 Probably less than 10%. Repeatable performance tests would be nice.

>
> Regards,
> chenwj
>
> --
> Wei-Ren Chen (陳韋任)
> Computer Systems Lab, Institute of Information Science,
> Academia Sinica, Taiwan (R.O.C.)
> Tel:886-2-2788-3799 #1667
> Homepage: http://people.cs.nctu.edu.tw/~chenwj

Re: [Qemu-devel] x86 AREG0 patches

[Andreas Färber]

Am 13.05.2012 23:04, schrieb Blue Swirl:
> A preview of x86 AREG0 patches can be found at the usual place:
> URL	git://repo.or.cz/qemu/blueswirl.git
> 	http://repo.or.cz/r/qemu/blueswirl.git

It looks like that push has completely replaced your pending ppc conversion?

If someone needs it for testing I still have a rebased version here:
http://repo.or.cz/w/qemu/afaerber.git/shortlog/refs/heads/ppc

Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

Re: [Qemu-devel] x86 AREG0 patches

[Blue Swirl]

On Mon, May 14, 2012 at 10:02 PM, Andreas Färber <afaerber@suse.de> wrote:
> Am 13.05.2012 23:04, schrieb Blue Swirl:
>> A preview of x86 AREG0 patches can be found at the usual place:
>> URL   git://repo.or.cz/qemu/blueswirl.git
>>       http://repo.or.cz/r/qemu/blueswirl.git
>
> It looks like that push has completely replaced your pending ppc conversion?

Yes, I popped the StGit series before working on this, sorry. I really
should try to use git branches.

>
> If someone needs it for testing I still have a rebased version here:
> http://repo.or.cz/w/qemu/afaerber.git/shortlog/refs/heads/ppc

Would you like to start maintaining them in your queue?

>
> Andreas
>
> --
> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

Re: [Qemu-devel] x86 AREG0 patches

[Andreas Färber]

Am 15.05.2012 19:22, schrieb Blue Swirl:
> On Mon, May 14, 2012 at 10:02 PM, Andreas Färber <afaerber@suse.de> wrote:
>> Am 13.05.2012 23:04, schrieb Blue Swirl:
>>> A preview of x86 AREG0 patches can be found at the usual place:
>>> URL   git://repo.or.cz/qemu/blueswirl.git
>>>       http://repo.or.cz/r/qemu/blueswirl.git
>>
>> It looks like that push has completely replaced your pending ppc conversion?
> 
> Yes, I popped the StGit series before working on this, sorry. I really
> should try to use git branches.

If this StGit uses only one master branch, you can at least archive
multiple branches using

git push repo master:areg0-ppc

with repo as remote, master as local source branch and areg0-ppc as
remote destination branch name.

Locally you could create a branch with `git branch branchname`. `git
branch` tells you which branch you are on and `git checkout branchname`
switches between them. Pretty easy actually. The harder part is
organizing your branches in a way matching your workflows - I tend to do
lots of stuff in parallel, so by now I use at least ten local
repositories to avoid switching between branches and wasting time with
lengthy rebuilds, for working on different topics (e.g., master, 0.15,
ppc-next, s390-next, ARM, QOM).

I think Peter mentioned using StGit, and he maintains branches for his
PULLs.

>> If someone needs it for testing I still have a rebased version here:
>> http://repo.or.cz/w/qemu/afaerber.git/shortlog/refs/heads/ppc
> 
> Would you like to start maintaining them in your queue?

I don't want qom-next to turn into a general-purpose master replacement.

Instead I would like Alex as ppc maintainer to decide on a sequence for
applying our series to ppc-next, and I'd either pull or cherry-pick the
QOM-related parts from there (don't think we have a conflict so far).

Note that my branch doesn't properly fix the build issue, it just added
a quick build fix on top for testing. On Alex' branch it seemed fixed
properly but wasn't rebased yet when I tested tcg/ppc64.

Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg