On Sun, Dec 16, 2012 at 06:11:14PM +0200, Michael S. Tsirkin wrote:
> On Fri, Dec 14, 2012 at 12:45:16PM +0100, Stefan Hajnoczi wrote:
> > On Wed, Dec 12, 2012 at 4:49 PM, Michael S. Tsirkin wrote:
> > > On Wed, Dec 12, 2012 at 04:34:21PM +0100, Stefan Hajnoczi wrote:
> > >> On Tue, Dec 11, 2012 a
On Fri, Dec 14, 2012 at 12:45:16PM +0100, Stefan Hajnoczi wrote:
> On Wed, Dec 12, 2012 at 4:49 PM, Michael S. Tsirkin wrote:
> > On Wed, Dec 12, 2012 at 04:34:21PM +0100, Stefan Hajnoczi wrote:
> >> On Tue, Dec 11, 2012 at 08:09:56PM +0200, Michael S. Tsirkin wrote:
> >> > On Tue, Dec 11, 2012 at
On Wed, Dec 12, 2012 at 4:49 PM, Michael S. Tsirkin wrote:
> On Wed, Dec 12, 2012 at 04:34:21PM +0100, Stefan Hajnoczi wrote:
>> On Tue, Dec 11, 2012 at 08:09:56PM +0200, Michael S. Tsirkin wrote:
>> > On Tue, Dec 11, 2012 at 10:32:28AM -0600, Anthony Liguori wrote:
>> > > "Michael S. Tsirkin" wr
On Wed, Dec 12, 2012 at 04:34:21PM +0100, Stefan Hajnoczi wrote:
> On Tue, Dec 11, 2012 at 08:09:56PM +0200, Michael S. Tsirkin wrote:
> > On Tue, Dec 11, 2012 at 10:32:28AM -0600, Anthony Liguori wrote:
> > > "Michael S. Tsirkin" writes:
> > >
> > > > On Tue, Dec 11, 2012 at 04:27:49PM +0100, St
On Tue, Dec 11, 2012 at 08:09:56PM +0200, Michael S. Tsirkin wrote:
> On Tue, Dec 11, 2012 at 10:32:28AM -0600, Anthony Liguori wrote:
> > "Michael S. Tsirkin" writes:
> >
> > > On Tue, Dec 11, 2012 at 04:27:49PM +0100, Stefan Hajnoczi wrote:
> > >> On Tue, Dec 11, 2012 at 3:13 PM, Michael S. Tsi
On Tue, Dec 11, 2012 at 10:32:28AM -0600, Anthony Liguori wrote:
> "Michael S. Tsirkin" writes:
>
> > On Tue, Dec 11, 2012 at 04:27:49PM +0100, Stefan Hajnoczi wrote:
> >> On Tue, Dec 11, 2012 at 3:13 PM, Michael S. Tsirkin
> >> wrote:
> >> > On Mon, Dec 10, 2012 at 02:09:36PM +0100, Stefan Haj
"Michael S. Tsirkin" writes:
> On Tue, Dec 11, 2012 at 04:27:49PM +0100, Stefan Hajnoczi wrote:
>> On Tue, Dec 11, 2012 at 3:13 PM, Michael S. Tsirkin wrote:
>> > On Mon, Dec 10, 2012 at 02:09:36PM +0100, Stefan Hajnoczi wrote:
>> >> The data plane thread needs to map guest physical addresses to
On Tue, Dec 11, 2012 at 04:27:49PM +0100, Stefan Hajnoczi wrote:
> On Tue, Dec 11, 2012 at 3:13 PM, Michael S. Tsirkin wrote:
> > On Mon, Dec 10, 2012 at 02:09:36PM +0100, Stefan Hajnoczi wrote:
> >> The data plane thread needs to map guest physical addresses to host
> >> pointers. Normally this
On Tue, Dec 11, 2012 at 3:13 PM, Michael S. Tsirkin wrote:
> On Mon, Dec 10, 2012 at 02:09:36PM +0100, Stefan Hajnoczi wrote:
>> The data plane thread needs to map guest physical addresses to host
>> pointers. Normally this is done with cpu_physical_memory_map() but the
>> function assumes the gl
On Mon, Dec 10, 2012 at 02:09:36PM +0100, Stefan Hajnoczi wrote:
> The data plane thread needs to map guest physical addresses to host
> pointers. Normally this is done with cpu_physical_memory_map() but the
> function assumes the global mutex is held. The data plane thread does
> not touch the g
The data plane thread needs to map guest physical addresses to host
pointers. Normally this is done with cpu_physical_memory_map() but the
function assumes the global mutex is held. The data plane thread does
not touch the global mutex and therefore needs a thread-safe memory
mapping mechanism.
11 matches
Mail list logo