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


Groups > linux.kernel > #1200547 > unrolled thread

Re: [PATCH 5/8] x86/vm86: Add a separate config option for hardware IRQ handling

Started byIngo Molnar <mingo@kernel.org>
First post2015-08-05 11:00 +0200
Last post2015-08-05 11:00 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH 5/8] x86/vm86: Add a separate config option for hardware  IRQ handling Ingo Molnar <mingo@kernel.org> - 2015-08-05 11:00 +0200

#1200547 — Re: [PATCH 5/8] x86/vm86: Add a separate config option for hardware IRQ handling

FromIngo Molnar <mingo@kernel.org>
Date2015-08-05 11:00 +0200
SubjectRe: [PATCH 5/8] x86/vm86: Add a separate config option for hardware IRQ handling
Message-ID<pU2Ik-4Ky-27@gated-at.bofh.it>
* Brian Gerst <brgerst@gmail.com> wrote:

> >> Disabling even less-used code that could have system stability impact. We've 
> >> discouraged user-mode drivers for a very long time.  Ironically, other than 
> >> being configured through the vm86 syscall, there isn't really anything 
> >> vm86-specific about it.  All it does is register an IRQ handler that sends a 
> >> signal to the task.
> >
> > So is this actually used by anything? Could we get away with disabling it, 
> > just to see whether anything cares?
> 
> My best guess would be some very old X11 drivers that needed interrupts to run 
> the Video BIOS code.

So let's keep it - but not complicate it with another layer of disabling logic. 
People that rely on legacies will enable vm86 as a single block - they won't 
necessarily know how deeply they rely on it.

What _would_ be useful is to have a 3-mode vm86 sysctl:

   1: enabled
   0: disabled
  -1: disabled permanently (one-shot disabling after bootup)

That way a distro can permanently disable vm86 for a particular bootup by setting 
it to -1 in /etc/sysctl.conf.

The kernel should default that setting to '0'.

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web