public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Stefani Seibold <stefani@seibold.net>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	x86@kernel.org, tglx@linutronix.de, mingo@redhat.com,
	ak@linux.intel.com, aarcange@redhat.com, john.stultz@linaro.org,
	luto@amacapital.net, xemul@parallels.com, gorcunov@openvz.org,
	andriy.shevchenko@linux.intel.com,
	Martin.Runge@rohde-schwarz.com, Andreas.Brief@rohde-schwarz.com
Subject: Re: [PATCH v15 0/10] Add 32 bit VDSO time function support
Date: Thu, 13 Feb 2014 23:50:08 -0800	[thread overview]
Message-ID: <52FDCAB0.2090509@zytor.com> (raw)
In-Reply-To: <1392364081.1034.6.camel@wall-e.seibold.net>

On 02/13/2014 11:48 PM, Stefani Seibold wrote:
> Am Donnerstag, den 13.02.2014, 22:47 -0800 schrieb H. Peter Anvin:
>> Hi,
>>
>> I tried this patchset, but it fails to compile on i386 "make allyesconfig".
>>
>> 	-hpa
>>
> 
> I tried "make allyseconfig" on my i386, but the resulting config will
> always set CONFIG_X86_64=y, so it fails with

"make ARCH=i386 allyesconfig"

... will do it for you.

> scripts/mod/empty.c:1:0: error: CPU you selected does not support x86-64
> instruction set
> 
> Setting to CONFIG_X86_32 by hand will allow to compile but fails in
> vclock_gettime.c, because CONFIG_PARAVIRT_CLOCK is not supported for by
> a 32 bit VDSO.

Right, this is the problem here.  Keep in mind many shipping kernels
will have CONFIG_PARAVIRT_CLOCK enabled, so it matters that a PV kernel
*booting native* doesn't take an unnecessary hit.

> PARAVIRT_CLOCK and getcpu is an other topic which is not addressed by
> this patch set.
> 
> I will do a patch to fix this.

Thanks.

	-hpa



      reply	other threads:[~2014-02-14  7:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-12 20:37 [PATCH v15 0/10] Add 32 bit VDSO time function support stefani
2014-02-12 20:37 ` [PATCH v15 01/10] Make vsyscall_gtod_data handling x86 generic stefani
2014-02-12 20:37 ` [PATCH v15 02/10] Add new func _install_special_mapping() to mmap.c stefani
2014-02-12 20:37 ` [PATCH v15 03/10] revamp vclock_gettime.c stefani
2014-02-12 20:37 ` [PATCH v15 04/10] vclock_gettime.c __vdso_clock_gettime cleanup stefani
2014-02-12 20:37 ` [PATCH v15 05/10] replace VVAR(vsyscall_gtod_data) by gtod macro stefani
2014-02-12 20:37 ` [PATCH v15 06/10] cleanup __vdso_gettimeofday stefani
2014-02-12 20:38 ` [PATCH v15 07/10] introduce VVAR marco for vdso32 stefani
2014-02-12 20:38 ` [PATCH v15 08/10] Add 32 bit VDSO time support for 32 bit kernel stefani
2014-02-12 20:38 ` [PATCH v15 09/10] Add 32 bit VDSO time support for 64 " stefani
2014-02-14  6:47 ` [PATCH v15 0/10] Add 32 bit VDSO time function support H. Peter Anvin
2014-02-14  7:48   ` Stefani Seibold
2014-02-14  7:50     ` H. Peter Anvin [this message]

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=52FDCAB0.2090509@zytor.com \
    --to=hpa@zytor.com \
    --cc=Andreas.Brief@rohde-schwarz.com \
    --cc=Martin.Runge@rohde-schwarz.com \
    --cc=aarcange@redhat.com \
    --cc=ak@linux.intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=gorcunov@openvz.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=mingo@redhat.com \
    --cc=stefani@seibold.net \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=xemul@parallels.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox