On Tue, Nov 21, 2017 at 05:58:12PM +0100, Igor Mammedov wrote:
> anyways, if you prefer having mixed endianness here, I won't mind much,
> as impact of test case is much smaller so we'll see down the road
> if it became any better.
I agree here.
> (as far as we continue going in direction
> of us
On Tue, 21 Nov 2017 18:31:19 +0200
"Michael S. Tsirkin" wrote:
> On Tue, Nov 21, 2017 at 05:22:36PM +0100, Igor Mammedov wrote:
> > > > > > > > probably it's been discussed but, why not do
> > > > > > > > leXX_to_cpu()
> > > > > > > > here, instead of making each place that access read field
> >
On Tue, Nov 21, 2017 at 05:22:36PM +0100, Igor Mammedov wrote:
> > > > > > > probably it's been discussed but, why not do
> > > > > > > leXX_to_cpu()
> > > > > > > here, instead of making each place that access read field
> > > > > > > to do leXX_to_cpu() manually.?
> > > > > > >
> > > > > > > Be
On Tue, 21 Nov 2017 18:02:48 +0200
"Michael S. Tsirkin" wrote:
> On Tue, Nov 21, 2017 at 04:58:09PM +0100, Igor Mammedov wrote:
> > On Tue, 21 Nov 2017 16:47:11 +0200
> > "Michael S. Tsirkin" wrote:
> >
> > > On Tue, Nov 21, 2017 at 02:26:39PM +0100, Igor Mammedov wrote:
> > > > On Mon, 20
On Tue, Nov 21, 2017 at 04:58:09PM +0100, Igor Mammedov wrote:
> On Tue, 21 Nov 2017 16:47:11 +0200
> "Michael S. Tsirkin" wrote:
>
> > On Tue, Nov 21, 2017 at 02:26:39PM +0100, Igor Mammedov wrote:
> > > On Mon, 20 Nov 2017 22:32:29 +0200
> > > "Michael S. Tsirkin" wrote:
> > >
> > > > On Mo
On Tue, 21 Nov 2017 16:47:11 +0200
"Michael S. Tsirkin" wrote:
> On Tue, Nov 21, 2017 at 02:26:39PM +0100, Igor Mammedov wrote:
> > On Mon, 20 Nov 2017 22:32:29 +0200
> > "Michael S. Tsirkin" wrote:
> >
> > > On Mon, Nov 20, 2017 at 05:55:22PM +0100, Igor Mammedov wrote:
> > > > On Thu, 16
On Tue, Nov 21, 2017 at 02:26:39PM +0100, Igor Mammedov wrote:
> On Mon, 20 Nov 2017 22:32:29 +0200
> "Michael S. Tsirkin" wrote:
>
> > On Mon, Nov 20, 2017 at 05:55:22PM +0100, Igor Mammedov wrote:
> > > On Thu, 16 Nov 2017 13:17:02 +0100
> > > Thomas Huth wrote:
> > >
> > > > The bios-table
On Mon, 20 Nov 2017 22:32:29 +0200
"Michael S. Tsirkin" wrote:
> On Mon, Nov 20, 2017 at 05:55:22PM +0100, Igor Mammedov wrote:
> > On Thu, 16 Nov 2017 13:17:02 +0100
> > Thomas Huth wrote:
> >
> > > The bios-tables-test was writing out files that we pass to iasl in
> > > with the wrong endia
On Mon, Nov 20, 2017 at 05:55:22PM +0100, Igor Mammedov wrote:
> On Thu, 16 Nov 2017 13:17:02 +0100
> Thomas Huth wrote:
>
> > The bios-tables-test was writing out files that we pass to iasl in
> > with the wrong endianness in the header when running on a big endian
> > host. So instead of storin
On 20.11.2017 17:55, Igor Mammedov wrote:
> On Thu, 16 Nov 2017 13:17:02 +0100
> Thomas Huth wrote:
>
>> The bios-tables-test was writing out files that we pass to iasl in
>> with the wrong endianness in the header when running on a big endian
>> host. So instead of storing mixed endian informati
On Thu, 16 Nov 2017 13:17:02 +0100
Thomas Huth wrote:
> The bios-tables-test was writing out files that we pass to iasl in
> with the wrong endianness in the header when running on a big endian
> host. So instead of storing mixed endian information in our structures,
> let's keep everything in li
The bios-tables-test was writing out files that we pass to iasl in
with the wrong endianness in the header when running on a big endian
host. So instead of storing mixed endian information in our structures,
let's keep everything in little endian and byte-swap it only when we
need a value in the co
12 matches
Mail list logo
