Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1350841

Re: soft lockup when passing vvar address to write(2)

From Thomas Gleixner <tglx@linutronix.de>
Newsgroups linux.kernel
Subject Re: soft lockup when passing vvar address to write(2)
Date 2016-03-05 09:30 +0100
Message-ID <r9fL4-3nX-7@gated-at.bofh.it> (permalink)
References <r8KnU-5IL-21@gated-at.bofh.it> <r8LDk-6HH-19@gated-at.bofh.it> <r8Slr-38B-1@gated-at.bofh.it> <r97DQ-5Ye-13@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Fri, 4 Mar 2016, Andy Lutomirski wrote:
> Thomas, I still think we should consider just deleting the HPET vclock
> code and accept the syscall overhead on systems that are stuck using
> HPET.  If fast syscalls are available (which should include every
> system with HPET, unless there are some 32-bit AMD systems lying
> around), then the overhead in a syscall is *tiny* compared to the code
> of the HPET read itself.

No objection from my side, really.

Thanks,

	tglx

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Re: soft lockup when passing vvar address to write(2) Andy Lutomirski <luto@amacapital.net> - 2016-03-05 00:50 +0100
  Re: soft lockup when passing vvar address to write(2) Thomas Gleixner <tglx@linutronix.de> - 2016-03-05 09:30 +0100
    Re: soft lockup when passing vvar address to write(2) Ingo Molnar <mingo@kernel.org> - 2016-03-05 10:10 +0100
      Re: soft lockup when passing vvar address to write(2) Andy Lutomirski <luto@amacapital.net> - 2016-03-06 04:00 +0100

csiph-web