On Wed, Nov 30, 2016 at 11:09:28AM -0200, Eduardo Habkost wrote:
> On Tue, Nov 29, 2016 at 09:54:29PM -0200, Marcelo Tosatti wrote:
> > On Tue, Nov 29, 2016 at 10:34:05AM -0200, Eduardo Habkost wrote:
> > > On Tue, Nov 29, 2016 at 08:56:00AM -0200, Marcelo Tosatti wrote:
> > > > On Mon, Nov 28,
When passed to git-diff (and to every other git command producing diffs
and/or diffstats) with "-O" or "diff.orderFile", this list of patterns
will place the more declarative / abstract hunks first, while changes to
imperative code / details will be near the end of the patches. This saves
on
On 2 December 2016 at 10:12, Liviu Ionescu wrote:
> I see your point, and I'm convinced that for your use cases booting
> linux and starting applications is a big deal of effort.
>
> for the bare metal use cases, "going through the bootup process"
> is quite lightwheight, setting
On Wed, Nov 30, 2016 at 03:48:01PM -0500, John Snow wrote:
> On 11/30/2016 07:03 AM, Laszlo Ersek wrote:
> > On 11/30/16 11:55, Gerd Hoffmann wrote:
> >> On Mi, 2016-11-30 at 11:08 +0100, Laszlo Ersek wrote:
> >>> Recent git releases support the diff.orderFile permanent setting.
> >>
> >> Cool.
>
On 11/30/16 13:27, Fam Zheng wrote:
> On Wed, 11/30 13:03, Laszlo Ersek wrote:
>> On 11/30/16 11:55, Gerd Hoffmann wrote:
>>> On Mi, 2016-11-30 at 11:08 +0100, Laszlo Ersek wrote:
Recent git releases support the diff.orderFile permanent setting.
>>>
>>> Cool.
>>>
configure
On Thu, Dec 01, 2016 at 09:35:27AM -0500, Paolo Bonzini wrote:
> > > > Maybe we could do the same for sockets? When data is available on a
> > > > socket (or when it becomes writable), write to a user memory location.
> > > >
> > > > I, too, have an interest in polling; in my situation most of
> On 2 Dec 2016, at 11:40, Peter Maydell wrote:
>
>> ... integrate this feature in the usual debugging workflow.
>
> The most useful approach is that you can set up a complicated
> situation (eg "boot my embedded RTOS, start application"),
> snapshot at that point,
On Thu, Dec 01, 2016 at 11:36:55AM -0600, Wei Huang wrote:
>
>
> On 12/01/2016 03:18 AM, Andrew Jones wrote:
> > On Wed, Nov 30, 2016 at 11:16:41PM -0600, Wei Huang wrote:
> >> From: Christopher Covington
> >>
> >> Ensure that reads of the PMCCNTR_EL0 are monotonically
On 1 December 2016 at 19:45, Liviu Ionescu wrote:
>
>> On 1 Dec 2016, at 21:13, Peter Maydell wrote:
>>
>> You need a QCOW2 disk to store the snapshots on, ...
>> Taking savevm snapshots doesn't need any cooperation
>> from the guest OS ..
>> I don't
Hi Vladimir,
On Thu, Dec 01, 2016 at 02:26:28PM +0300, Vladimir Sementsov-Ogievskiy wrote:
> 01.12.2016 13:14, Wouter Verhelst wrote:
[...]
> > -- `NBD_ALLOC_ADD_CONTEXT` (2): the list of allocation contexts
> > +- `NBD_META_ADD_CONTEXT` (2): the list of metadata contexts
> >
02.12.2016 02:42, John Snow wrote:
(B) In the case of "User just wanted to look around," the bitmap should
be merged back into the bitmap it was forked from.
currently existing example: "failed incremental backup"
--
Best regards,
Vladimir
On Fri, Dec 02, 2016 at 04:17:50PM +1100, Benjamin Herrenschmidt wrote:
> On Fri, 2016-12-02 at 15:18 +1100, David Gibson wrote:
> > But if you pass through multiple groups, things get weird. On q35,
> > you'd generally expect physically separate (different slot) devices to
> > appear under
> v4:
> * Added poll time self-tuning algorithm [Christian and Paolo]
> * Try a single iteration of polling to avoid non-blocking
> ppoll(2)/epoll_wait(2) [Paolo]
> * Reordered patches to make performance analysis easier - see below
Reviewed-by: Paolo Bonzini
> v3:
>
On Fri, 2 Dec 2016 15:42:49 +1100
Sam Bobroff wrote:
> Ping?
>
The issue got addressed by this commit:
commit 0d594f5565837fe2886a8aa307ef8abb65eab8f7
Author: Thomas Huth
Date: Wed Sep 21 11:42:15 2016 +0200
ppc/kvm: Mark 64kB page size
101 - 114 of 114 matches
Mail list logo