From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Bamvor Jian Zhang <bamvor.zhangjian@linaro.org>,
y2038@lists.linaro.org, gregkh@linuxfoundation.org,
broonie@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Y2038] [PATCH v2 2/2] ppdev: add support for compat ioctl
Date: Sat, 2 Jan 2016 11:59:29 +0530 [thread overview]
Message-ID: <20160102062929.GA10432@sudip-pc> (raw)
In-Reply-To: <9555229.aJQNyGf9cL@wuerfel>
On Fri, Jan 01, 2016 at 11:09:45PM +0100, Arnd Bergmann wrote:
> On Friday 01 January 2016 10:34:25 Sudip Mukherjee wrote:
> > > Did you happen to check with both 32-bit and 64-bit user space on a
> > > 64-bit kernel? This is one of the things that was not working originally
> > > but should work now.
> >
> > I dont think I can manage 32 bit userspace on 64-bit kernel here. But I
> > can definitely check it on a kvm guest.
>
> Just to be sure we are talking about the same thing: you mean running a 64-bit
> kernel in a kvm guest with a 32-bit file system, right? Running a 32-bit
> kvm guest on a 64-bit host would not be interesting of course.
The kvm (actually qemu, started from virt-manager with -enable-kvm) that
I just configured shows the following:
lscpu shows:
Architecture: i686
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 1
On-line CPU(s) list: 0
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 6
Stepping: 3
CPU MHz: 2993.200
BogoMIPS: 5986.40
Virtualization: VT-x
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 32K
L1i cache: 32K
L2 cache: 4096K
uname -i shows:
i686
Will it be ok to test in this one?
regards
sudip
next prev parent reply other threads:[~2016-01-02 6:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 9:58 [PATCH v2 0/2] Convert ppdev to y2038 safe Bamvor Jian Zhang
2015-12-17 9:58 ` [PATCH v2 1/2] ppdev: convert " Bamvor Jian Zhang
2015-12-17 9:58 ` [PATCH v2 2/2] ppdev: add support for compat ioctl Bamvor Jian Zhang
2015-12-17 23:12 ` Arnd Bergmann
2015-12-30 11:16 ` Sudip Mukherjee
2015-12-30 13:24 ` Bamvor Jian Zhang
2015-12-30 13:48 ` Sudip Mukherjee
2015-12-30 13:51 ` [Y2038] " Arnd Bergmann
2015-12-30 14:20 ` Bamvor Jian Zhang
2015-12-31 9:43 ` Sudip Mukherjee
2015-12-31 14:12 ` Arnd Bergmann
2016-01-01 5:04 ` Sudip Mukherjee
2016-01-01 22:09 ` Arnd Bergmann
2016-01-02 6:29 ` Sudip Mukherjee [this message]
2016-01-02 22:40 ` Arnd Bergmann
2016-01-04 13:14 ` Sudip Mukherjee
2016-01-04 13:26 ` Arnd Bergmann
2016-01-06 12:56 ` Bamvor Jian Zhang
2016-01-07 15:12 ` Arnd Bergmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160102062929.GA10432@sudip-pc \
--to=sudipm.mukherjee@gmail.com \
--cc=arnd@arndb.de \
--cc=bamvor.zhangjian@linaro.org \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=y2038@lists.linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.