search for: tty_io

Ok, so I think I have a complete explanation for the difference between the *BSD behaviour and the Linux/Solaris behaviour. Well, almost complete :) Pull out your trusty copies of "The Design and Implementation of the 4.4BSD Operating System" as well as "Unix Internals: The New Frontiers". Specifically, pages 111-112 and 344 of the former and page 108 of the latter. It comes

On Wed, Oct 11, 2017 at 01:30:15PM -0700, Thomas Garnier wrote: > Provide an option to default visibility to hidden except for key > symbols. This option is disabled by default and will be used by x86_64 > PIE support to remove errors between compilation units. > > The default visibility is also enabled for external symbols that are > compared as they maybe equals (start/end of

On Wed, Oct 11, 2017 at 01:30:15PM -0700, Thomas Garnier wrote: > Provide an option to default visibility to hidden except for key > symbols. This option is disabled by default and will be used by x86_64 > PIE support to remove errors between compilation units. > > The default visibility is also enabled for external symbols that are > compared as they maybe equals (start/end of

....../accel/habanalabs/common/habanalabs_ioctl.c | 15 +++++---------- > .../gpu/drm/i915/display/intel_display_driver.c | 10 ++++------ > drivers/gpu/drm/nouveau/nouveau_chan.c | 4 +--- > drivers/gpu/drm/nouveau/nouveau_drm.c | 7 +++---- > drivers/tty/tty_io.c | 5 ++--- FOr tty: Reviewed-by: Jiri Slaby <jirislaby at kernel.org> thanks, -- js suse labs

...4 ++-- drivers/infiniband/hw/cxgb4/resource.c | 9 +++++---- drivers/net/sc92031.c | 16 ++++++---------- drivers/target/tcm_fc/tfc_io.c | 4 ++-- drivers/tty/moxa.c | 5 +++-- drivers/tty/mxser.c | 4 ++-- drivers/tty/tty_io.c | 4 ++-- drivers/usb/atm/usbatm.c | 4 ++-- drivers/usb/class/usblp.c | 7 +++---- drivers/usb/wusbcore/wa-xfer.c | 7 +++---- drivers/xen/xenbus/xenbus_xs.c | 4 ++-- net/can/af_can.c | 5 +++--...

...4 ++-- drivers/infiniband/hw/cxgb4/resource.c | 9 +++++---- drivers/net/sc92031.c | 16 ++++++---------- drivers/target/tcm_fc/tfc_io.c | 4 ++-- drivers/tty/moxa.c | 5 +++-- drivers/tty/mxser.c | 4 ++-- drivers/tty/tty_io.c | 4 ++-- drivers/usb/atm/usbatm.c | 4 ++-- drivers/usb/class/usblp.c | 7 +++---- drivers/usb/wusbcore/wa-xfer.c | 7 +++---- drivers/xen/xenbus/xenbus_xs.c | 4 ++-- net/can/af_can.c | 5 +++--...

...4 ++-- drivers/infiniband/hw/cxgb4/resource.c | 9 +++++---- drivers/net/sc92031.c | 16 ++++++---------- drivers/target/tcm_fc/tfc_io.c | 4 ++-- drivers/tty/moxa.c | 5 +++-- drivers/tty/mxser.c | 4 ++-- drivers/tty/tty_io.c | 4 ++-- drivers/usb/atm/usbatm.c | 4 ++-- drivers/usb/class/usblp.c | 7 +++---- drivers/usb/wusbcore/wa-xfer.c | 7 +++---- drivers/xen/xenbus/xenbus_xs.c | 4 ++-- net/can/af_can.c | 5 +++--...

...lity ("default"))) > > Does this still work with CONFIG_LD_DEAD_CODE_DATA_ELIMINATION ? I cannot make it work with or without this change. How is it supposed to be used? For me with, it crashes with a bad consdev at: http://elixir.free-electrons.com/linux/latest/source/drivers/tty/tty_io.c#L3194 > >> +#else >> +#define __default_visibility >> +#endif >> + >> /* >> * Generic compiler-dependent macros required for kernel >> * build go below this comment. Actual compiler/compiler version >> diff --git a/init/Kconfig b/init/Kconf...

...nouveau/nouveau_drv.c | 8 +- drivers/gpu/drm/radeon/radeon_device.c | 10 ++-- drivers/serial/sb1250-duart.c | 2 +- drivers/staging/msm/msm_fb.c | 8 +- drivers/staging/olpc_dcon/olpc_dcon.c | 10 ++-- drivers/staging/sm7xx/smtcfb.c | 8 +- drivers/tty/tty_io.c | 4 +- drivers/tty/vt/selection.c | 4 +- drivers/tty/vt/vc_screen.c | 16 ++-- drivers/tty/vt/vt.c | 124 ++++++++++++++++---------------- drivers/tty/vt/vt_ioctl.c | 60 ++++++++-------- drivers/video/arkfb.c...

...nouveau/nouveau_drv.c | 8 +- drivers/gpu/drm/radeon/radeon_device.c | 10 ++-- drivers/serial/sb1250-duart.c | 2 +- drivers/staging/msm/msm_fb.c | 8 +- drivers/staging/olpc_dcon/olpc_dcon.c | 10 ++-- drivers/staging/sm7xx/smtcfb.c | 8 +- drivers/tty/tty_io.c | 4 +- drivers/tty/vt/selection.c | 4 +- drivers/tty/vt/vc_screen.c | 16 ++-- drivers/tty/vt/vt.c | 124 ++++++++++++++++---------------- drivers/tty/vt/vt_ioctl.c | 60 ++++++++-------- drivers/video/arkfb.c...

...nouveau/nouveau_drv.c | 8 +- drivers/gpu/drm/radeon/radeon_device.c | 10 ++-- drivers/serial/sb1250-duart.c | 2 +- drivers/staging/msm/msm_fb.c | 8 +- drivers/staging/olpc_dcon/olpc_dcon.c | 10 ++-- drivers/staging/sm7xx/smtcfb.c | 8 +- drivers/tty/tty_io.c | 4 +- drivers/tty/vt/selection.c | 4 +- drivers/tty/vt/vc_screen.c | 16 ++-- drivers/tty/vt/vt.c | 124 ++++++++++++++++---------------- drivers/tty/vt/vt_ioctl.c | 60 ++++++++-------- drivers/video/arkfb.c...

...| 2 drivers/char/Makefile | 1 drivers/char/compat_mtio.c | 81 drivers/char/ftape/zftape/zftape-init.c | 1 drivers/char/n_tty.c | 1 drivers/char/raw.c | 91 drivers/char/tty_io.c | 191 + drivers/char/viotape.c | 1 drivers/char/vt.c | 3 drivers/char/vt_ioctl.c | 195 + drivers/i2c/i2c-dev.c | 141 + drivers/ide/ide-cd.c | 1 d...

...| 2 drivers/char/Makefile | 1 drivers/char/compat_mtio.c | 81 drivers/char/ftape/zftape/zftape-init.c | 1 drivers/char/n_tty.c | 1 drivers/char/raw.c | 91 drivers/char/tty_io.c | 191 + drivers/char/viotape.c | 1 drivers/char/vt.c | 3 drivers/char/vt_ioctl.c | 195 + drivers/i2c/i2c-dev.c | 141 + drivers/ide/ide-cd.c | 1 d...

Hi, Is the http://xenbits.xensource.com/linux-2.6-xen.hg tree still being updated? if not, what''s the preferred Linux tree to track that has all of the Xen bits? Thanks, Muli _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...m/x86/intel_oaktrail.c | 10 ++--- drivers/rapidio/rio-sysfs.c | 4 +- drivers/scsi/a3000.c | 2 +- drivers/sh/intc/core.c | 4 +- drivers/tty/hvc/hvcs.c | 2 +- drivers/tty/tty_io.c | 4 +- drivers/video/fbdev/aty/radeon_base.c | 4 +- drivers/video/fbdev/core/fbmon.c | 4 +- drivers/video/fbdev/pxafb.c | 7 ++-- kernel/trace/trace_benchmark.c | 4 +- lib/cpu_rmap.c...

...m/x86/intel_oaktrail.c | 10 ++--- drivers/rapidio/rio-sysfs.c | 4 +- drivers/scsi/a3000.c | 2 +- drivers/sh/intc/core.c | 4 +- drivers/tty/hvc/hvcs.c | 2 +- drivers/tty/tty_io.c | 4 +- drivers/video/fbdev/aty/radeon_base.c | 4 +- drivers/video/fbdev/core/fbmon.c | 4 +- drivers/video/fbdev/pxafb.c | 7 ++-- kernel/trace/trace_benchmark.c | 4 +- lib/cpu_rmap.c...

...m/x86/intel_oaktrail.c | 10 ++--- drivers/rapidio/rio-sysfs.c | 4 +- drivers/scsi/a3000.c | 2 +- drivers/sh/intc/core.c | 4 +- drivers/tty/hvc/hvcs.c | 2 +- drivers/tty/tty_io.c | 4 +- drivers/video/fbdev/aty/radeon_base.c | 4 +- drivers/video/fbdev/core/fbmon.c | 4 +- drivers/video/fbdev/pxafb.c | 7 ++-- kernel/trace/trace_benchmark.c | 4 +- lib/cpu_rmap.c...

xenconsole fix. reference of tty->count in xencons_close() is racy. It must be protected by tty_sem semaphore like con_close() in drivers/char/vt.c -- yamahata _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi Andi, This patch series implements the Linux Xen guest as a paravirt_ops backend. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen hvc console (console=hvc0) *

Hi Andi, This patch series implements the Linux Xen guest as a paravirt_ops backend. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen hvc console (console=hvc0) *