On Wed, Jun 18, 2014 at 02:35:21PM +0200, Greg Kurz wrote:
> On Wed, 18 Jun 2014 18:38:14 +0800
> Stefan Hajnoczi wrote:
>
> > On Tue, Jun 17, 2014 at 09:40:19AM +0200, Alexander Graf wrote:
> > >
> > > On 17.06.14 09:36, Stefan Hajnoczi wrote:
> > > >On Fri, Jun 13, 2014 at 01:18:00PM +0200, Gr
On 18.06.14 17:40, Peter Maydell wrote:
On 18 June 2014 16:37, Alexander Graf wrote:
I actually agree with Greg here. We implicitly create different VGA adapters
today depending on TARGET_WORDS_BIGENDIAN. The FB endianness should have
been separate devices (BE / LE) or runtime configuration fr
On 18 June 2014 16:37, Alexander Graf wrote:
> I actually agree with Greg here. We implicitly create different VGA adapters
> today depending on TARGET_WORDS_BIGENDIAN. The FB endianness should have
> been separate devices (BE / LE) or runtime configuration from the beginning.
>
> Anything that ch
On 18.06.14 17:35, Peter Maydell wrote:
On 18 June 2014 15:28, Greg Kurz wrote:
On Wed, 18 Jun 2014 16:42:04 +0300
"Michael S. Tsirkin" wrote:
On Wed, Jun 18, 2014 at 01:53:15PM +0100, Peter Maydell wrote:
On 18 June 2014 11:38, Stefan Hajnoczi wrote:
What bothers me is that real hardware
On 18 June 2014 15:28, Greg Kurz wrote:
> On Wed, 18 Jun 2014 16:42:04 +0300
> "Michael S. Tsirkin" wrote:
>> On Wed, Jun 18, 2014 at 01:53:15PM +0100, Peter Maydell wrote:
>> > On 18 June 2014 11:38, Stefan Hajnoczi wrote:
>> > > What bothers me is that real hardware can't do this.
>> >
>> > Re
On Wed, Jun 18, 2014 at 05:14:17PM +0200, Alexander Graf wrote:
>
> On 18.06.14 17:12, Michael S. Tsirkin wrote:
> >On Wed, Jun 18, 2014 at 02:35:21PM +0200, Greg Kurz wrote:
> >>On Wed, 18 Jun 2014 18:38:14 +0800
> >>Stefan Hajnoczi wrote:
> >>
> >>>On Tue, Jun 17, 2014 at 09:40:19AM +0200, Alex
On 18.06.14 17:12, Michael S. Tsirkin wrote:
On Wed, Jun 18, 2014 at 02:35:21PM +0200, Greg Kurz wrote:
On Wed, 18 Jun 2014 18:38:14 +0800
Stefan Hajnoczi wrote:
On Tue, Jun 17, 2014 at 09:40:19AM +0200, Alexander Graf wrote:
On 17.06.14 09:36, Stefan Hajnoczi wrote:
On Fri, Jun 13, 2014 a
On Wed, Jun 18, 2014 at 02:35:21PM +0200, Greg Kurz wrote:
> On Wed, 18 Jun 2014 18:38:14 +0800
> Stefan Hajnoczi wrote:
>
> > On Tue, Jun 17, 2014 at 09:40:19AM +0200, Alexander Graf wrote:
> > >
> > > On 17.06.14 09:36, Stefan Hajnoczi wrote:
> > > >On Fri, Jun 13, 2014 at 01:18:00PM +0200, Gr
On Wed, Jun 18, 2014 at 04:28:04PM +0200, Greg Kurz wrote:
> On Wed, 18 Jun 2014 16:42:04 +0300
> "Michael S. Tsirkin" wrote:
> > On Wed, Jun 18, 2014 at 01:53:15PM +0100, Peter Maydell wrote:
> > > On 18 June 2014 11:38, Stefan Hajnoczi wrote:
> > > > What bothers me is that real hardware can't
On Wed, 18 Jun 2014 16:42:04 +0300
"Michael S. Tsirkin" wrote:
> On Wed, Jun 18, 2014 at 01:53:15PM +0100, Peter Maydell wrote:
> > On 18 June 2014 11:38, Stefan Hajnoczi wrote:
> > > What bothers me is that real hardware can't do this.
> >
> > Real hardware doesn't have "endianness matches gues
On Wed, Jun 18, 2014 at 01:53:15PM +0100, Peter Maydell wrote:
> On 18 June 2014 11:38, Stefan Hajnoczi wrote:
> > What bothers me is that real hardware can't do this.
>
> Real hardware doesn't have "endianness matches guest CPU endianness"
> semantics, which is what the virtio spec mandates...
On 18 June 2014 11:38, Stefan Hajnoczi wrote:
> What bothers me is that real hardware can't do this.
Real hardware doesn't have "endianness matches guest CPU endianness"
semantics, which is what the virtio spec mandates...
> Given that VIRTIO
> 1.0 is always little-endian I guess this is just a
On Wed, 18 Jun 2014 18:38:14 +0800
Stefan Hajnoczi wrote:
> On Tue, Jun 17, 2014 at 09:40:19AM +0200, Alexander Graf wrote:
> >
> > On 17.06.14 09:36, Stefan Hajnoczi wrote:
> > >On Fri, Jun 13, 2014 at 01:18:00PM +0200, Greg Kurz wrote:
> > >>This version merges the changes requested during the
On Tue, Jun 17, 2014 at 09:40:19AM +0200, Alexander Graf wrote:
>
> On 17.06.14 09:36, Stefan Hajnoczi wrote:
> >On Fri, Jun 13, 2014 at 01:18:00PM +0200, Greg Kurz wrote:
> >>This version merges the changes requested during the v7 review, remarks from
> >>ppc64 dump support review (yes, we talked
On 17.06.14 09:36, Stefan Hajnoczi wrote:
On Fri, Jun 13, 2014 at 01:18:00PM +0200, Greg Kurz wrote:
This version merges the changes requested during the v7 review, remarks from
ppc64 dump support review (yes, we talked about virtio there) and the work on
virtio subsections migration. Also two
On Fri, Jun 13, 2014 at 01:18:00PM +0200, Greg Kurz wrote:
> This version merges the changes requested during the v7 review, remarks from
> ppc64 dump support review (yes, we talked about virtio there) and the work on
> virtio subsections migration. Also two new patches have been added:
> - patch #
On (Mon) 16 Jun 2014 [17:07:01], Greg Kurz wrote:
> Hi,
>
> I've reworked the patch set according to Alex's last remarks. Do any of the
> other maintainers have pending remarks ? Should I wait or send a v9 now ?
I'm yet to go through the series; I'll get to it in a day or two.
Am
On Fri, 13 Jun 2014 13:56:13 +0200
Alexander Graf wrote:
>
> On 13.06.14 13:18, Greg Kurz wrote:
> > Hi,
> >
> > This version merges the changes requested during the v7 review, remarks from
> > ppc64 dump support review (yes, we talked about virtio there) and the work
> > on
> > virtio subsectio
On 13.06.14 13:18, Greg Kurz wrote:
Hi,
This version merges the changes requested during the v7 review, remarks from
ppc64 dump support review (yes, we talked about virtio there) and the work on
virtio subsections migration. Also two new patches have been added:
- patch #1 is a preliminary fix
Hi,
This version merges the changes requested during the v7 review, remarks from
ppc64 dump support review (yes, we talked about virtio there) and the work on
virtio subsections migration. Also two new patches have been added:
- patch #1 is a preliminary fix for virtio-serial posted by Alexander G
20 matches
Mail list logo
