qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Large patch set advice


From: Kamil Rytarowski
Subject: Re: [Qemu-devel] Large patch set advice
Date: Thu, 26 Apr 2018 13:22:36 +0200
User-agent: Mozilla/5.0 (X11; NetBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0

On 26.04.2018 10:11, Peter Maydell wrote:
> On 25 April 2018 at 20:57, Warner Losh <address@hidden> wrote:
>> I’ve foolishly volunteered to rebase all the changes that the bad-user
>> mode folks have done to a recent master rev to get these changes upstreamed.
>> A number of people have been working on this for a long time. It’s possible
>> now to run almost any FreeBSD binary from all the architectures. We use it
>> to do ‘native’ builds of tens of thousands of packages in a chroot (so
>> building FreeBSD/arm packages on a FreeBSD amd64 box). The diffs are quite
>> large (on the order of 42k lines), so I anticipate some bumps in moving
>> this stuff upstream.
> 
> So, first up, thanks for agreeing to do this. It sounds from your
> mail like you're already pretty well aware of the usual pitfalls
> with this kind of work, and I don't really have much to add that's
> QEMU specific that nobody else has said already.
> 
> One question I do have is about the other BSDs: bsd-user at least
> in theory is supposed to support freebsd, netbsd and openbsd.
> Your patchsets should fix freebsd, but do you know what the status
> is of netbsd and openbsd? Upstream we do compiletest but no runtime
> testing; I think last time I tried it they didn't work very well,
> but it would be worth checking with the other BSDs downstream to
> see if they're using bsd-user and to make sure we don't break anything
> that is currently working for netbsd/openbsd...
> 

I'm looking forward to see it updated for FreeBSD first. We can
reschedule NetBSD part for later.

Feel free to CC me for code review.

> thanks
> -- PMM
> 


Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]