Luis R. Rodriguez | 29 Aug 02:17 2015

[RFC] asm-generic/pci_iomap.h: make custom PCI BAR requirements explicit

From: "Luis R. Rodriguez" <mcgrof <at> suse.com>

The S390 architecture requires a custom pci_iomap() implementation
as the asm-generic implementation assumes there are disjunctions
between PCI BARs, and on S390 PCI BAR are not disjunctive, S390 requires
the bar parameter in order to find the corresponding device and create
the mapping cookie.

This clash with the asm-generic pci_iomap() implementation is implicit,
there are no current semantics to make this incompatability explicit.
Make the S390 PCI BAR non-disjunction incompatibility explicit, and
also pave the way for alternative incompatibilities to be defined.

While at it, as with the ioremap*() variants, since we have no clear
semantics yet well defined provide a solution for them that returns
NULL. This allows architectures to move forward by defining pci_ioremap*()
variants without requiring immediate changes to all architectures. Each
architecture then can implement their own solution as needed and
when they get to it.

Build tested with allyesconfig on:

	* S390
	* x86_64

Signed-off-by: Luis R. Rodriguez <mcgrof <at> suse.com>
---

This came up as an idea after noting that S390 has no way to be
explicit about its requirements, this also means we don't have a
(Continue reading)

[tip:core/rcu] rcu,locking: Privatize smp_mb__after_unlock_lock()

Commit-ID:  12d560f4ea87030667438a169912380be00cea4b
Gitweb:     http://git.kernel.org/tip/12d560f4ea87030667438a169912380be00cea4b
Author:     Paul E. McKenney <paulmck <at> linux.vnet.ibm.com>
AuthorDate: Tue, 14 Jul 2015 18:35:23 -0700
Committer:  Paul E. McKenney <paulmck <at> linux.vnet.ibm.com>
CommitDate: Tue, 4 Aug 2015 08:49:21 -0700

rcu,locking: Privatize smp_mb__after_unlock_lock()

RCU is the only thing that uses smp_mb__after_unlock_lock(), and is
likely the only thing that ever will use it, so this commit makes this
macro private to RCU.

Signed-off-by: Paul E. McKenney <paulmck <at> linux.vnet.ibm.com>
Cc: Will Deacon <will.deacon <at> arm.com>
Cc: Peter Zijlstra <peterz <at> infradead.org>
Cc: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
Cc: "linux-arch <at> vger.kernel.org" <linux-arch <at> vger.kernel.org>
---
 Documentation/memory-barriers.txt   | 71 +++----------------------------------
 arch/powerpc/include/asm/spinlock.h |  2 --
 include/linux/spinlock.h            | 10 ------
 kernel/rcu/tree.h                   | 12 +++++++
 4 files changed, 16 insertions(+), 79 deletions(-)

diff --git a/Documentation/memory-barriers.txt b/Documentation/memory-barriers.txt
index 3185238..eafa6a5 100644
--- a/Documentation/memory-barriers.txt
+++ b/Documentation/memory-barriers.txt
 <at>  <at>  -1854,16 +1854,10  <at>  <at>  RELEASE are to the same lock variable, but only from the perspective of
(Continue reading)

Paul E. McKenney | 25 Aug 02:03 2015
Picon

[GIT PULL rcu/next] Additional RCU commit for 4.3

Hello, Ingo,

This additional series contains a single change:

1.	Privatize smp_mb__after_unlock_lock().  This commit moves the
	definition of smp_mb__after_unlock_lock() to kernel/rcu/tree.h,
	in recognition of the fact that RCU is the only thing using
	this, that nothing else is likely to use it, and that it is
	likely to go away completely.

This change has been subjected to 0day Test Robot and -next testing,
and is available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git for-mingo

for you to fetch changes up to 12d560f4ea87030667438a169912380be00cea4b:

  rcu,locking: Privatize smp_mb__after_unlock_lock() (2015-08-04 08:49:21 -0700)

----------------------------------------------------------------
Paul E. McKenney (1):
      rcu,locking: Privatize smp_mb__after_unlock_lock()

 Documentation/memory-barriers.txt   | 71 +++----------------------------------
 arch/powerpc/include/asm/spinlock.h |  2 --
 include/linux/spinlock.h            | 10 ------
 kernel/rcu/tree.h                   | 12 +++++++
 4 files changed, 16 insertions(+), 79 deletions(-)

(Continue reading)

Alexey Brodkin | 24 Aug 16:20 2015

[PATCH v3 0/6] ARCv2 port to Linux - (C) perf

Hi Peter,

This mini-series adds perf support for ARCv2 based cores, which brings in
overflow interupts and SMP. Additionally now raw events are supported as well.

Please review !

Compared to v2 this series has:
 [1] Removed patch with raw-events support.
     It needs some rework and let's then discuss it separately.
     Still I plan to send it shortly.
 [2] Merged "set usable max period as a half of real max period" into
     "implement "event_set_period".
 [3] Fixed arc_pmu_event_set_period() in regard of incorrect
     "hwc->period_left" setup.
 [4] Moved interrupts enabling from arc_pmu_add() to arc_pmu_start()

Compared to v1 this series has:
 [1] Addressed review comments
 [2] More verbose commit messages and comments in sources
 [3] Minor cosmetics

Thanks,
Alexey

Alexey Brodkin (4):
  ARCv2: perf: implement "event_set_period"
  ARCv2: perf: Support sampling events using overflow interrupts
  ARCv2: perf: implement exclusion of event counting in user or kernel
    mode
(Continue reading)

Maria-Elisabeth Schaeffler | 21 Aug 20:41 2015
Picon

FINANCIAL GIFT

I intend to give to you a portion of my Wealth as a free-will financial donation to you. Respond now to partake.

Regards
Maria-Elisabeth Schaeffler
Email:mariaelisabt <at> outlook.com

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

christain147 | 19 Aug 15:01 2015
Picon

Re:

Good day,hoping you read this email and respond to me in good time.I do not intend to solicit for funds but 
your time and energy in using my own resources to assist the less privileged.I am medically confined at the
moment hence I request your indulgence.
I will give you a comprehensive brief once I hear from you.

Please forward your response to my private email address:
gudworks104 <at> yahoo.com

Thanks and reply.

Robert Grondahl
Yuriy Kolerov | 17 Aug 17:52 2015

[PATCH] ARC: add negative dependency for VGA_CONSOLE

Architectures which support VGA console must define screen_info
structurture from "uapi/linux/screen_info.h". Otherwise undefined
symbol error occurs. Usually it's defined in "setup.c" for each
architecture.

If an architecture does not support VGA console (ARC's case)
there are 2 ways: define a dummy instance of screen_info or add
a negative dependency for VGA_CONSOLE in to prevent selecting
this option.

I've implemented the second way. However the best solution is to
add HAVE_VGA_CONSOLE option for targets which support VGA
console. Then turn off VGA_CONSOLE by default and add dependency
to HAVE_VGA_CONSOLE. But right now it's better to just add a
negative dependency for ARC and then consider how to collaborate
about this issue with maintainers of other architectures.

Signed-off-by: Yuriy Kolerov <yuriy.kolerov <at> synopsys.com>
---
 drivers/video/console/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/video/console/Kconfig b/drivers/video/console/Kconfig
index fe1cd01..5d27ba0 100644
--- a/drivers/video/console/Kconfig
+++ b/drivers/video/console/Kconfig
 <at>  <at>  -9,7 +9,7  <at>  <at>  config VGA_CONSOLE
 	depends on !4xx && !8xx && !SPARC && !M68K && !PARISC && !FRV && \
 		!SUPERH && !BLACKFIN && !AVR32 && !MN10300 && !CRIS && \
 		(!ARM || ARCH_FOOTBRIDGE || ARCH_INTEGRATOR || ARCH_NETWINDER) && \
(Continue reading)

James Hogan | 7 Aug 17:21 2015
James Hogan <james.hogan <at> imgtec.com>

Subject: [PATCH v2 00/11] test_user_copy improvements

[PATCH v2 00/11] test_user_copy improvements

These patches extend the test_user_copy test module to handle lots more
cases of user accessors which architectures can override separately, and
in particular those which are important for checking the MIPS Enhanced
Virtual Addressing (EVA) implementations, which need to handle
overlapping user and kernel address spaces, with special instructions
for accessing user address space from kernel mode.

- Checking that kernel pointers are accepted when user address limit is
  set to KERNEL_DS, as done by the kernel when it internally invokes
  system calls with kernel pointers.
- Checking of the unchecked accessors (which don't call access_ok()).
  Some of the tests are special cased for EVA at the moment which has
  stricter hardware guarantees for bad user accesses than other
  configurations.
- Checking of other sets of user accessors, including the inatomic user
  copies, clear_user, compatibility accessors (copy_in_user and
  _unaligned), the user string accessors, and the user checksum
  functions, all of which need special handling in arch code with EVA.

Tested on MIPS with and without EVA, and on x86_64.

Only build tested for arm, blackfin, metag, microblaze, openrisc,
parisc, powerpc, sh, sparc, tile, i386 & xtensa.

All arches were audited for the appropriate exports, only score is known
to still be missing some.

Changes in v2:
- Add arch exports (patches 1-4).
- Reorder patches slightly.
(Continue reading)

Mark Salter | 6 Aug 23:41 2015
Picon

[PATCH V2 0/3] mm: Add generic copy from early unmapped RAM

When booting an arm64 kernel w/initrd using UEFI/grub, use of mem= will likely
cut off part or all of the initrd. This leaves it outside the kernel linear
map which leads to failure when unpacking. The x86 code has a similar need to
relocate an initrd outside of mapped memory in some cases.

The current x86 code uses early_memremap() to copy the original initrd from
unmapped to mapped RAM. This patchset creates a generic copy_from_early_mem()
utility based on that x86 code and has arm64 and x86 share it in their
respective initrd relocation code.

Changes from V1:

  * Change cover letter subject to highlight the added generic code

  * Add patch for x86 to use common copy_from_early_mem()

Mark Salter (3):
  mm: add utility for early copy from unmapped ram
  arm64: support initrd outside kernel linear map
  x86: use generic early mem copy

 arch/arm64/kernel/setup.c           | 55 +++++++++++++++++++++++++++++++++++++
 arch/x86/kernel/setup.c             | 21 +-------------
 include/asm-generic/early_ioremap.h |  6 ++++
 mm/early_ioremap.c                  | 22 +++++++++++++++
 4 files changed, 84 insertions(+), 20 deletions(-)

--

-- 
2.4.3

(Continue reading)

Arguinchona, Christa L | 6 Aug 12:20 2015
Picon

This Message is From the Administrator Desk

Due to our latest IP Security upgrades we have reason to believe that your web mail account was accessed by a
third party. Protecting the security of your web mail account is our primary concern, we have limited
access to sensitive web mail account features.Failure to re-validate, your e-mail will be blocked in 24
hours. To Confirm Your E-mail Account click on the link below.

http://scb.moy.su/emailupgrade.htm

Thank you for your cooperation.
System Administrator.

________________________________

This message is intended for the sole use of the addressee, and may contain information that is privileged,
confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby
notified that you may not use, copy, disclose, or distribute to anyone the message or any information
contained in the message. If you have received this message in error, please immediately advise the
sender by reply email and delete this message.
James Hogan | 5 Aug 17:48 2015
James Hogan <james.hogan <at> imgtec.com>

Subject: [PATCH 0/7] test_user_copy improvements

[PATCH 0/7] test_user_copy improvements

These patches extend the test_user_copy test module to handle lots more
cases of user accessors which architectures can override separately, and
in particular those which are important for checking the MIPS Enhanced
Virtual Addressing (EVA) implementations, which need to handle
overlapping user and kernel address spaces, with special instructions
for accessing user address space from kernel mode.

- Checking that kernel pointers are accepted when user address limit is
  set to KERNEL_DS, as done by the kernel when it internally invokes
  system calls with kernel pointers.
- Checking of the unchecked accessors (which don't call access_ok()).
  Some of the tests are special cased for EVA at the moment which has
  stricter hardware guarantees for bad user accesses than other
  configurations.
- Checking of other sets of user accessors, including the inatomic user
  copies, copy_in_user, clear_user, the user string accessors, and the
  user checksum functions, all of which need special handling in arch
  code with EVA.

Tested on MIPS with and without EVA, and on x86_64.

James Hogan (7):
  test_user_copy: Check legit kernel accesses
  test_user_copy: Check unchecked accessors
  test_user_copy: Check __clear_user()/clear_user()
  test_user_copy: Check __copy_in_user()/copy_in_user()
  test_user_copy: Check __copy_{to,from}_user_inatomic()
  test_user_copy: Check user string accessors
  test_user_copy: Check user checksum functions

(Continue reading)


Gmane