Daniel P Berrange writes:
> On Tue, Sep 13, 2016 at 08:36:25PM +0200, Lluís Vilanova wrote:
>> Daniel P Berrange writes:
>>
>> > On Thu, Sep 08, 2016 at 03:23:26PM +0200, Lluís Vilanova wrote:
>> >> Daniel P Berrange writes:
>> >>
>> >> > I previously split the global trace-events file up into
Daniel P Berrange writes:
> On Fri, Sep 09, 2016 at 03:16:50PM +0200, Lluís Vilanova wrote:
>> > The various _DSTATE variables are still arbitrarily scattered in
>> > memory, as opposed to in a contiguous cache friendly array, which
>> > is one of the goals of Paolo's original change.
>>
>> >
On Tue, Sep 13, 2016 at 08:36:25PM +0200, Lluís Vilanova wrote:
> Daniel P Berrange writes:
>
> > On Thu, Sep 08, 2016 at 03:23:26PM +0200, Lluís Vilanova wrote:
> >> Daniel P Berrange writes:
> >>
> >> > I previously split the global trace-events file up into one file
> >> > per-subdirectory to
Daniel P Berrange writes:
> On Thu, Sep 08, 2016 at 03:23:26PM +0200, Lluís Vilanova wrote:
>> Daniel P Berrange writes:
>>
>> > I previously split the global trace-events file up into one file
>> > per-subdirectory to avoid merge conflict hell.
>> [...]
>>
>> Sorry, I could not find the
On Fri, Sep 09, 2016 at 03:16:50PM +0200, Lluís Vilanova wrote:
> > The various _DSTATE variables are still arbitrarily scattered in
> > memory, as opposed to in a contiguous cache friendly array, which
> > is one of the goals of Paolo's original change.
>
> > That said, I'm unclear on how much
On Thu, Sep 08, 2016 at 03:23:26PM +0200, Lluís Vilanova wrote:
> Daniel P Berrange writes:
>
> > I previously split the global trace-events file up into one file
> > per-subdirectory to avoid merge conflict hell.
> [...]
>
> Sorry, I could not find the message where the infrastructure is
On Tue, Sep 13, 2016 at 06:05:07PM +0200, Lluís Vilanova wrote:
> Daniel P Berrange writes:
>
> > On Tue, Sep 13, 2016 at 03:54:01PM +0100, Stefan Hajnoczi wrote:
> >> Dan: Ping?
> >>
> >> A few people have reviewed this series. A v2 would be appreciated. I'd
> >> like to merge it quickly and
Daniel P Berrange writes:
> On Tue, Sep 13, 2016 at 03:54:01PM +0100, Stefan Hajnoczi wrote:
>> Dan: Ping?
>>
>> A few people have reviewed this series. A v2 would be appreciated. I'd
>> like to merge it quickly and as early into the development cycle as
>> possible.
> Sorry, been focused on
On Tue, Sep 13, 2016 at 03:54:01PM +0100, Stefan Hajnoczi wrote:
> Dan: Ping?
>
> A few people have reviewed this series. A v2 would be appreciated. I'd
> like to merge it quickly and as early into the development cycle as
> possible.
Sorry, been focused on other series, but will try and post
Dan: Ping?
A few people have reviewed this series. A v2 would be appreciated. I'd
like to merge it quickly and as early into the development cycle as
possible.
Stefan
signature.asc
Description: PGP signature
Daniel P Berrange writes:
> On Fri, Sep 09, 2016 at 01:03:51PM +0200, Lluís Vilanova wrote:
>> Daniel P Berrange writes:
>>
>> > On Thu, Sep 08, 2016 at 03:23:26PM +0200, Lluís Vilanova wrote:
>> >> Daniel P Berrange writes:
>> >>
>> >> > I previously split the global trace-events file up into
On Fri, Sep 09, 2016 at 01:03:51PM +0200, Lluís Vilanova wrote:
> Daniel P Berrange writes:
>
> > On Thu, Sep 08, 2016 at 03:23:26PM +0200, Lluís Vilanova wrote:
> >> Daniel P Berrange writes:
> >>
> >> > I previously split the global trace-events file up into one file
> >> > per-subdirectory to
Daniel P Berrange writes:
> On Thu, Sep 08, 2016 at 03:23:26PM +0200, Lluís Vilanova wrote:
>> Daniel P Berrange writes:
>>
>> > I previously split the global trace-events file up into one file
>> > per-subdirectory to avoid merge conflict hell.
>> [...]
>>
>> Sorry, I could not find the
Daniel P Berrange writes:
> I previously split the global trace-events file up into one file
> per-subdirectory to avoid merge conflict hell.
[...]
Sorry, I could not find the message where the infrastructure is modified to
provide this. But I think there's a more efficient way to provide
On Thu, Sep 08, 2016 at 03:23:26PM +0200, Lluís Vilanova wrote:
> Daniel P Berrange writes:
>
> > I previously split the global trace-events file up into one file
> > per-subdirectory to avoid merge conflict hell.
> [...]
>
> Sorry, I could not find the message where the infrastructure is
On 10/08/2016 10:39, Fam Zheng wrote:
> Then the script needs to be updated to work with different package management
> systems (rpm and deb). For now they only call standard Linux commands. That's
> least of the problem, though.
>
> The more tricky question is how the script can tell which
On Wed, Aug 10, 2016 at 04:05:06PM +0200, Lluís Vilanova wrote:
> Daniel P Berrange writes:
>
> > I previously split the global trace-events file up into one file
> > per-subdirectory to avoid merge conflict hell.
>
> > This series builds on that to now actually generate the individual
> > trace
Daniel P Berrange writes:
> I previously split the global trace-events file up into one file
> per-subdirectory to avoid merge conflict hell.
> This series builds on that to now actually generate the individual
> trace files per-subdirectory too. The key benefit of doing this is
> that a change
On Wed, Aug 10, 2016 at 04:39:21PM +0800, Fam Zheng wrote:
> On Wed, 08/10 09:24, Daniel P. Berrange wrote:
> > On Wed, Aug 10, 2016 at 04:13:10PM +0800, Fam Zheng wrote:
> > > On Wed, 08/10 09:06, Daniel P. Berrange wrote:
> > > > On Wed, Aug 10, 2016 at 09:41:40AM +0800, Fam Zheng wrote:
> > > >
On Wed, 08/10 09:24, Daniel P. Berrange wrote:
> On Wed, Aug 10, 2016 at 04:13:10PM +0800, Fam Zheng wrote:
> > On Wed, 08/10 09:06, Daniel P. Berrange wrote:
> > > On Wed, Aug 10, 2016 at 09:41:40AM +0800, Fam Zheng wrote:
> > > > On Tue, 08/09 18:11, Daniel P. Berrange wrote:
> > > > >
> > > >
On Wed, Aug 10, 2016 at 04:13:10PM +0800, Fam Zheng wrote:
> On Wed, 08/10 09:06, Daniel P. Berrange wrote:
> > On Wed, Aug 10, 2016 at 09:41:40AM +0800, Fam Zheng wrote:
> > > On Tue, 08/09 18:11, Daniel P. Berrange wrote:
> > > >
> > > > Can we get this report to include details of the
> > > >
On Wed, 08/10 09:06, Daniel P. Berrange wrote:
> On Wed, Aug 10, 2016 at 09:41:40AM +0800, Fam Zheng wrote:
> > On Tue, 08/09 18:11, Daniel P. Berrange wrote:
> > >
> > > Can we get this report to include details of the
> > >
> > > a) the software versions of gcc, binutils, and any -devel
On Wed, Aug 10, 2016 at 09:41:40AM +0800, Fam Zheng wrote:
> On Tue, 08/09 18:11, Daniel P. Berrange wrote:
> >
> > Can we get this report to include details of the
> >
> > a) the software versions of gcc, binutils, and any -devel packages
> > we're building against
> >
> > b) the
On Tue, 08/09 18:11, Daniel P. Berrange wrote:
> so we don't have to go digging into the docker test systemm to
> try and reverse engineer this info
Actually, digging this info is pretty easy if you already use docker test
locally (if you don't, may I ask why?). Just append DEBUG=1 and you can
On Tue, 08/09 18:11, Daniel P. Berrange wrote:
>
> Can we get this report to include details of the
>
> a) the software versions of gcc, binutils, and any -devel packages
> we're building against
>
> b) the exact arguments + env variables used to invoke configure,
> not merely its
ally.
>
> Message-id: 1470756748-18933-1-git-send-email-berra...@redhat.com
> Type: series
> Subject: [Qemu-devel] [PATCH for-2.8 v1 00/60] Modular build of trace event
> files
>
> === TEST SCRIPT BEGIN ===
> #!/bin/bash
> set -e
> git submodule update --init dtc
>
Hi,
Your series failed automatic build test. Please find the testing commands and
their output below. If you have docker installed, you can probably reproduce it
locally.
Message-id: 1470756748-18933-1-git-send-email-berra...@redhat.com
Type: series
Subject: [Qemu-devel] [PATCH for-2.8 v1 00/60
I previously split the global trace-events file up into one file
per-subdirectory to avoid merge conflict hell.
This series builds on that to now actually generate the individual
trace files per-subdirectory too. The key benefit of doing this is
that a change in a trace-events file will no longer
28 matches
Mail list logo
