On Fri, Jul 06, 2012 at 10:05:48PM +0100, Catalin Marinas wrote:
> +++ b/arch/aarch64/include/asm/assembler.h
> @@ -0,0 +1,143 @@
> +/*
> + * Based on arch/arm/include/asm/assembler.h
> + *
> + * Copyright (C) 1996-2000 Russell King
> + * Copyright (C) 2012 ARM Ltd.
> + *
> + * This program is
Hi,
I have a question on the code below:
void rt_mutex_setprio(struct task_struct *p, int prio)
{
...
if (on_rq)
enqueue_task(rq, p, oldprio < prio ? ENQUEUE_HEAD : 0);
When enqueueing @p with new @prio, it seems put @p at the head of a
rq if appropriate. I guess
06.07.2012 21:26, J. Bruce Fields пишет:
On Fri, Jul 06, 2012 at 05:45:56PM +0400, Stanislav Kinsbursky wrote:
This is a bug fix for 3.5 kernel.
In case on NFSd service start failure svc_shutdown_net() will call svc_destroy
callback and zeroize global nfsd_serv pointer, this in turn will lead
On Fri, Jul 6, 2012 at 7:17 AM, Paulo Marques wrote:
[...]
>
> There was a recent thread from David Brown on the arm linux mailing list
> ("ARM: two possible fixes for the KALLSYMS build problem"). He tracked
> down the problem to having empty per_cpu sections on a non-smp build.
Actually rmk
On Fri, Jul 06, 2012 at 02:33:15PM -0700, Tony Luck wrote:
> In commit dad1743e5993f19b3d7e7bd0fb35dc45b5326626
> x86/mce: Only restart instruction after machine check recovery if it is safe
> we fixed mce_notify_process() to force a signal to the current process
> if it was not restartable
Catalin,
On Fri, Jul 6, 2012 at 2:05 PM, Catalin Marinas wrote:
> This set of patches implements the core Linux support for the AArch64
> (64-bit ARM) architecture.
Hmm. I didn't see a cc to current ARM maintainer (Russell), nor did
you cc the topic list that you list in the MAINTAINERS entry.
On Fri, Jul 06, 2012 at 10:05:41PM +0100, Catalin Marinas wrote:
> There is no hardware platform available at this point. From a kernel
> perspective, the aim is to minimise (or even completely remove) the
> platform code from the architecture specific directory. FDT is currently
> mandated and
On 07/07/2012 08:43 AM, Tetsuo Handa wrote:
> Alex Shi wrote:
>> Thanks for your report, mm should means mm_struct. no vma. My fault.
>> Could you like try this patch.
>
> Builds OK. Thank you.
Uh, seems the allnoconfig setting is different on different tree.
I need to tired it other tree no
Em 06-07-2012 22:49, Du Changbin escreveu:
>>> diff --git a/drivers/media/rc/ati_remote.c
> b/drivers/media/rc/ati_remote.c
>>> index 7be377f..0df66ac 100644
>>> --- a/drivers/media/rc/ati_remote.c
>>> +++ b/drivers/media/rc/ati_remote.c
>>> @@ -23,6 +23,8 @@
>>> *Vincent
From: Ostrowski, Anthony Paul
Sent: Friday, July 06, 2012 9:43 PM
Subject: Contact Me For The Project Via: elizza_ett...@hotmail.com
I am Elizabeth.Etters, a devoted christian. I am setting up a charity
foundation but due to my health condition I would
On Fri, Jul 06, 2012 at 06:09:20PM +0100, Dave Airlie wrote:
> On Fri, Jul 6, 2012 at 5:49 PM, Dave Airlie wrote:
> > On Fri, Jul 6, 2012 at 3:48 PM, Fengguang Wu wrote:
> >> ... The missed kconfig.
> >>
> >> On Fri, Jul 06, 2012 at 10:46:22PM +0800, Fengguang Wu wrote:
> >>> Hi Thomas,
> >
> >
Dear RT Folks,
I'm pleased to announce the 3.2.22-rt34 stable release.
This release is just an update to the new stable 3.2.22 version
and no RT specific changes have been made.
You can get this release via the git tree at:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
What's the status of this patch? Forgotten, or are there still any outstanding
concerns?
On 03/02/2012 01:54 PM, Vivek Goyal wrote:
> Hi Jens,
>
> Do you have concerns about this patch? If no, can you please consider
> merging it.
>
> Thanks
>
> > diff --git a/drivers/media/rc/ati_remote.c
b/drivers/media/rc/ati_remote.c
> > index 7be377f..0df66ac 100644
> > --- a/drivers/media/rc/ati_remote.c
> > +++ b/drivers/media/rc/ati_remote.c
> > @@ -23,6 +23,8 @@
> >*Vincent Vanackere
> >*Added support for
Signed-off-by: Axel Lin
---
drivers/regulator/da9052-regulator.c |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/regulator/da9052-regulator.c
b/drivers/regulator/da9052-regulator.c
index 88976d8..5f8f71a 100644
--- a/drivers/regulator/da9052-regulator.c
+++
On Sat, Jul 7, 2012 at 1:32 AM, Scan Subscription
wrote:
>
> CID 200075: Free of array-typed value (BAD_FREE.array)
>
> /linux/fs/splice.c: 317 ( array_assign)
>311 struct page *pages[PIPE_DEF_BUFFERS];
>312
On Sat, 2012-07-07 at 06:07 +0900, OGAWA Hirofumi wrote:
> "Steven J. Magnani" writes:
>
> > On Wed, 2012-07-04 at 20:07 +0900, OGAWA Hirofumi wrote:
> >> Please don't add new lock_super() usage if it is not necessary. Almost
> >> all of lock_super() just replaced lock_kernel() usage. It
Hi, David
On Fri, 06 Jul 2012 11:27:39 -0600, David Ahern wrote:
> What config options need to be enabled for 'perf lock record' to work?
> I tried a number of custom builds and stock Fedora kernels. I always
> get:
>
> $ perf lock record -- sleep 1
> invalid or unsupported event:
Hi,
Theodore Ts'o wrote:
> On Fri, Jul 06, 2012 at 06:02:18PM -0500, Jonathan Nieder wrote:
>> Why cc: stable@? Does this fix a build error, oops, hang, data
>> corruption, real security issue, or other critical "oh, that's not
>> good" bug?
>
> All of the /dev/random patches in this patch
This is a patch to the ashmem.c file that fixes up several pr_info and pr_err
warnings found by the checkpath.pl tool
Signed-off-by: Pablo Vazquez Rodriguez
---
drivers/staging/android/ashmem.c | 13 +++--
1 files changed, 7 insertions(+), 6 deletions(-)
diff --git
On Fri, Jul 6, 2012 at 4:37 PM, Bill Unruh wrote:
> On Fri, 6 Jul 2012, Bjorn Helgaas wrote:
>
>> On Sat, Jun 02, 2012 at 11:30:23AM +0800, Jiang Liu wrote:
>>>
>>> ... address range 0xfed98000-0xfed9 has been reserved by motherboard
>>> device(PNP0C02).
No, pnp resource reservation is after
Alex Shi wrote:
> Thanks for your report, mm should means mm_struct. no vma. My fault.
> Could you like try this patch.
Builds OK. Thank you.
> From 97781231b130e7f7fced12244653ed9b9946c944 Mon Sep 17 00:00:00 2001
> From: Alex Shi
> Date: Fri, 6 Jul 2012 20:49:25 +0800
> Subject: [PATCH]
On Sat, Jul 07, 2012 at 01:58:24AM +0900, JoonSoo Kim wrote:
> 2012/7/7 Minchan Kim :
> > Hi Joonsoo,
> >
> > On Sat, Jul 07, 2012 at 12:28:41AM +0900, Joonsoo Kim wrote:
> >> __alloc_pages_direct_compact has many arguments so invoking it is very
> >> costly.
> >
> > It's already slow path so
On Fri, 6 Jul 2012, Greg Kroah-Hartman wrote:
> On Wed, Jun 27, 2012 at 09:19:15PM +0200, Jesper Juhl wrote:
> > My previous 14 patch series to vt6656 missed a few bits and
> > pieces. This mops up the last few obvious style issues.
> > It is quite short and completely trivial - simply deletes a
Use devm_gpio_request_one to save a few error handling code.
Also remove trivial comment for tps62360_remove.
Signed-off-by: Axel Lin
---
drivers/regulator/tps62360-regulator.c | 38 +++-
1 file changed, 8 insertions(+), 30 deletions(-)
diff --git
On Fri, 2012-07-06 at 14:25 -0700, Haiyang Zhang wrote:
> This adds support for setting synthetic NIC MAC address from within Linux
> guests. Before using this feature, the option "spoofing of MAC address"
> should be enabled at the Hyper-V manager / Settings of the synthetic
> NIC.
[...]
> +int
On Fri, 6 Jul 2012, Bjorn Helgaas wrote:
On Sat, Jun 02, 2012 at 11:30:23AM +0800, Jiang Liu wrote:
... address range 0xfed98000-0xfed9 has been reserved by motherboard
device(PNP0C02). I guess that BIOS has assigned address "0xfed98000" to
:00:04.0 for thermal management
On Wed, Jul 04, 2012 at 01:37:07AM +0300, Eduardo Valentin wrote:
> In the System Control Module, OMAP supplies a voltage reference
> and a temperature sensor feature that are gathered in the band
> gap voltage and temperature sensor (VBGAPTS) module. The band
> gap provides current and voltage
On Fri, Jul 06, 2012 at 06:02:18PM -0500, Jonathan Nieder wrote:
>
> Why cc: stable@? Does this fix a build error, oops, hang, data
> corruption, real security issue, or other critical "oh, that's not
> good" bug?
All of the /dev/random patches in this patch series that were marked
for the
On Fri, Jul 6, 2012 at 4:15 PM, Xiao Jiang wrote:
> 2012/7/6 Rob Herring
>>
>> On 07/06/2012 05:38 AM, jgq...@gmail.com wrote:
>> > From: Xiao Jiang
>> >
>> > Since more and more arm chips support device tree, it'd be better add
>> > PROC_DEVICETREE
>> > in arch/arm/Kconfig to avoid duplicate
On Fri, Jul 06, 2012 at 06:02:18PM -0500, Jonathan Nieder wrote:
> Hi,
>
> Theodore Ts'o wrote:
>
> > Send the USB device's serial, product, and manufacturer strings to the
> > /dev/random driver to help seed its pools.
> >
> > Cc: Linus Torvalds
> > Acked-by: Greg KH
> > Signed-off-by:
On Fri, Jun 29, 2012 at 07:48:45PM +0200, Pablo Vázquez wrote:
> Ok, added the #define pr_fmt(fmt) ...
You sent this in HTML format, makeing it impossible to apply :(
Care to try it again?
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
On Wed, Jun 27, 2012 at 09:19:15PM +0200, Jesper Juhl wrote:
> My previous 14 patch series to vt6656 missed a few bits and
> pieces. This mops up the last few obvious style issues.
> It is quite short and completely trivial - simply deletes a few blank
> lines, does some whitespace cleanup around
On Wed, Jun 27, 2012 at 02:10:15PM +0200, Javier M. Mellid wrote:
> From: "Javier M. Mellid"
>
> This patch erases hardcode cast between smtcfb_info and fb_info in order
> to get a more robust and less rigid smtcfb_info structure. fb_info
> doesn't need to be the first field in smtcfb_info after
Remove SWIOTLB overflow buffer support and return DMA_ERROR_CODE
(a value of zero) to make it consistent with iommu implementation
on Intel, AMD, and swiotlb-xen.
Tested only on x86.
Signed-off-by: Shuah Khan
---
lib/swiotlb.c | 44
1 file
Hi,
Theodore Ts'o wrote:
> Send the USB device's serial, product, and manufacturer strings to the
> /dev/random driver to help seed its pools.
>
> Cc: Linus Torvalds
> Acked-by: Greg KH
> Signed-off-by: "Theodore Ts'o"
> Cc: sta...@vger.kernel.org
Why cc: stable@? Does this fix a build
On Thu, Jun 28, 2012 at 02:01:00AM -0300, Sebastian Benvenuti wrote:
> fixed "many quoted string split across lines" issues,
> replaced "printk(KERN_ERR" for "pr_err("
> and replaced "printk(KERN_INFO" for "pr_info("
>
> Signed-off-by: Sebastian Benvenuti
Where was...
Ok, you get the idea now.
On Thu, Jun 28, 2012 at 01:47:09AM -0300, Sebastian Benvenuti wrote:
> Fixed +40 "quoted string split across lines" issues
> plus some lines that were over 80 chars
> and a "pr_info(" function replaced "printk(KERN_INFO"
>
> Signed-off-by: Sebastian Benvenuti
Where was patches 1/4, 2/4, and
> arch/x86/include/asm/atomic64_32.h |1 +
> arch/x86/include/asm/atomic64_64.h |1 +
> arch/xtensa/kernel/syscall.c|2 +-
This looks odd to say the least ?
The only other question I'd ask is given that ppc and x86 have both done
32/64bit
On Thu, Jun 28, 2012 at 01:28:20AM -0300, Sebastian Benvenuti wrote:
> changed 41 instances of printk(KERN_DEBUG for the prefered pr_debug(
>
> Signed-off-by: Sebastian Benvenuti
Where was patches 1/3 and 2/3?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
On Thu, Jun 28, 2012 at 01:23:47AM -0300, Sebastian Benvenuti wrote:
> changed 3 instances of printk(KERN_ERR for the prefered pr_err(
>
> Signed-off-by: Sebastian Benvenuti
Where was patch 1/2?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
On Thu, Jun 28, 2012 at 10:28:57PM -0300, Sebastian Benvenuti wrote:
> @@ -1462,7 +1461,7 @@ static int __init vmk80xx_init(void)
> {
> int retval;
>
> - printk(KERN_INFO "vmk80xx: version 0.8.01 "
> + pr_info("vmk80xx: version 0.8.01 " \
> "Manuel Gebele \n");
We've been moving away from add_interrupt_randomness() for various
reasons: it's too expensive to do on every interrupt, and flooding the
CPU with interrupts could theoretically cause bogus floods of entropy
from a somewhat externally controllable source.
This solves both problems by limiting the
From: Mark Brown
wm831x devices contain a unique ID value. Feed this into the newly added
device_add_randomness() to add some per device seed data to the pool.
Signed-off-by: Mark Brown
Signed-off-by: Theodore Ts'o
Cc: sta...@vger.kernel.org
---
drivers/mfd/wm831x-otp.c | 8
1 file
device_init_wakeup uses the dev_name() of the device to set the
name of the wakeup_source which appears in
/sys/kernel/debug/wakeup_sources.
For a platform device, that name is not set until platform_device_add
calls dev_set_name.
So the call to device_init_wakeup() must be after the call to
This version fixes some sparse complaints; reduces stack usage in
xfer_secondary_pool; fixes a lockdep complaint caused by
get_random_bytes() getting called from interrupt context; and other
minor updates as requested by patch reviewers.
- Ted
Linus
Create a new function, get_random_bytes_arch() which will use the
architecture-specific hardware random number generator if it is
present. Change get_random_bytes() to not use the HW RNG, even if it
is avaiable.
The reason for this is that the hw random number generator is fast (if
it is
Add extern and static declarations to suppress sparse warnings
Signed-off-by: "Theodore Ts'o"
---
drivers/char/random.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/char/random.c b/drivers/char/random.c
index 4ec04a7..cb541b9 100644
--- a/drivers/char/random.c
The real-time Linux folks don't like add_interrupt_randomness() taking
a spinlock since it is called in the low-level interrupt routine.
This also allows us to reduce the overhead in the fast path, for the
random driver, which is the interrupt collection path.
Signed-off-by: "Theodore Ts'o"
Cc:
Matt Mackall stepped down as the /dev/random driver maintainer last
year, so Theodore Ts'o is taking back the /dev/random driver.
Cc: Matt Mackall
Signed-off-by: "Theodore Ts'o"
---
MAINTAINERS | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
Signed-off-by: "Theodore Ts'o"
---
drivers/char/random.c | 26 ++--
include/trace/events/random.h | 134 ++
2 files changed, 156 insertions(+), 4 deletions(-)
create mode 100644 include/trace/events/random.h
diff --git
Cc: David Miller
Cc: Linus Torvalds
Signed-off-by: "Theodore Ts'o"
Cc: sta...@vger.kernel.org
---
net/core/dev.c | 3 +++
net/core/rtnetlink.c | 1 +
2 files changed, 4 insertions(+)
diff --git a/net/core/dev.c b/net/core/dev.c
index 6df2140..bdd1e88 100644
--- a/net/core/dev.c
+++
From: Mark Brown
The tamper evident features of the RTC include the "write counter" which
is a pseudo-random number regenerated whenever we set the RTC. Since this
value is unpredictable it should provide some useful seeding to the random
number generator.
Only do this on boot since the goal is
From: Linus Torvalds
Add a new interface, add_device_randomness() for adding data to the
random pool that is likely to differ between two devices (or possibly
even per boot). This would be things like MAC addresses or serial
numbers, or the read-out of the RTC. This does *not* add any actual
If the CPU supports a hardware random number generator, use it in
xfer_secondary_pool(), where it will significantly improve things and
where we can afford it.
Also, remove the use of the arch-specific rng in
add_timer_randomness(), since the call is significantly slower than
get_cycles(), and
Send the USB device's serial, product, and manufacturer strings to the
/dev/random driver to help seed its pools.
Cc: Linus Torvalds
Acked-by: Greg KH
Signed-off-by: "Theodore Ts'o"
Cc: sta...@vger.kernel.org
---
drivers/usb/core/hub.c | 9 +
1 file changed, 9 insertions(+)
diff
On Thu, 2012-07-05 at 10:44 +0800, Andy Green wrote:
[...]
> To make use of this safely you also need to make sure that any drivers that
> may compete for the bus ordinal you are using (eg, mUSB and ehci in Panda
> case) are loaded in a deterministic order.
[...]
This seems very restrictive...
Hello `./scripts/get_maintainer.pl -f drivers/usb/musb/omap2430.c`
omap2430_musb_set_vbus in omap2430.c contains:
while (musb_readb(musb->mregs, MUSB_DEVCTL) & 0x80) {
cpu_relax();
if (time_after(jiffies,
Hi Linus,
The following changes since commit ff826b2b5b269ad440afa686ede879ccabfda387:
Merge tag 'sound-3.5' of
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound (2012-07-03 11:10:18
-0700)
are available in the git repository at:
On Fri, Jul 6, 2012 at 3:05 PM, Jukka Ollila wrote:
>
> Now this got me wondering if Debian _unstable_ actually qualifies as a
> standard distro userspace.
Oh, if the kernel breaks some standard user space, that counts. Tons
of people run Debian unstable (and from my limited interactions with
On Fri, Jul 6, 2012 at 10:38 PM, Alan Cox wrote:
> On Fri, 6 Jul 2012 20:45:44 +0300
> Jukka Ollila wrote:
>> A few days ago I filed a kernel regression report concerning a change
>> in /proc/kmsg behaviour with short reads:
>>
>> https://bugzilla.kernel.org/show_bug.cgi?id=44211
>> I don't
On Fri, Jul 6, 2012 at 7:18 AM, Jan Beulich wrote:
> Now that the x86_phys_bits cpuinfo field is uniformly available on
> 32- and 64-bit, the function no longer needs to determine this anew.
>
> Additionally, both size_or_mask and size_and_mask can be set once at
> the end of the function instead
In commit dad1743e5993f19b3d7e7bd0fb35dc45b5326626
x86/mce: Only restart instruction after machine check recovery if it is safe
we fixed mce_notify_process() to force a signal to the current process
if it was not restartable (RIPV bit not set in MCG_STATUS). But doing
it here means that the
On Sat, Jul 07, 2012 at 12:59:44AM +0300, Aaro Koskinen wrote:
> Hi,
>
> On Fri, Jul 06, 2012 at 05:38:50PM -0400, Theodore Ts'o wrote:
> > I couldn't remember whether the canonical marking is sta...@kernel.org
> > or sta...@vger.kernel.org, so I went looking, and discovered that it
> > wasn't
On Thu, Jul 05, 2012 at 03:01:12PM -0400, Eric Wustrow wrote:
> Will this do the long path in add_interrupt_randomness every 16 interrupts
> instead of 128?
Yes, but given that benchmarks didn't show any performance degradation
even under a worst case scenario (i.e., no interrupt mitigation, and
Hi,
On Fri, Jul 06, 2012 at 05:38:50PM -0400, Theodore Ts'o wrote:
> I couldn't remember whether the canonical marking is sta...@kernel.org
> or sta...@vger.kernel.org, so I went looking, and discovered that it
> wasn't mentioned in the kernel sources. You can find mention of it in
> Greg K-H's
Kernel style uses parenthesis around sizeof.
Signed-off-by: Joe Perches
---
scripts/checkpatch.pl |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index 7190f95..a743622 100755
--- a/scripts/checkpatch.pl
+++
I am seeing somewhat very high power consumption usage of the network
device and backlight
Here is what report powertop, network can go as high as 9W
8.03 W100.0% Device Display backlight
5.19 W 23.1 pkts/sDevice Network
interface:
I couldn't remember whether the canonical marking is sta...@kernel.org
or sta...@vger.kernel.org, so I went looking, and discovered that it
wasn't mentioned in the kernel sources. You can find mention of it in
Greg K-H's blog, but not everyone would necessarily find this blog
entry.
On Fri, Jul 6, 2012 at 7:14 AM, Jan Beulich wrote:
> Needing to deal with potentially large memory configurations, the
> variables here should be "unsigned long" instead of "unsigned int".
>
> Signed-off-by: Jan Beulich
>
> ---
> arch/x86/kernel/cpu/mtrr/generic.c |8
> 1 file
On Fri, Jul 6, 2012 at 1:38 PM, Bjorn Helgaas wrote:
> pci :0b:00.0: reg 10: [mem 0xf1eff000-0xf1ef]
> -pci :00:1c.1: BAR 15: assigned [mem 0xf020-0xf03f 64bit pref]
> +pci :00:1c.1: bridge window [io 0x1000-0x0fff] to [bus 0b-0b]
> add_size 1000
> +pci :00:1c.1:
On 07/06/2012 03:05 PM, Catalin Marinas wrote:
> The patch adds the kernel booting and the initial setup code.
> Documentation/aarch64/booting.txt describes the booting protocol on the
> AArch64 Linux kernel. This is subject to change following the work on
> boot standardisation, ACPI.
> diff
Em 04-07-2012 05:08, Du, Changbin escreveu:
> changes:
> 1. break some lines that are longer than 80 characters.
> 2. remove local function prototype declarations which do not
> need.
> 3. replace TAB character with a space character in function
> comments.
>
On Fri, Jul 06, 2012 at 11:23:52PM +0200, Christian Lamparter wrote:
> The idea of moving rebind procedure into pm.complete
> was taken from the usb-subsystem, which has similar
> problems with reattaching devices during/after
> resume.
>
> Signed-off-by: Christian Lamparter
> ---
> To Greg:
>
Em 04-07-2012 00:11, Du, Changbin escreveu:
> Make it possible to specify allowed RC protocols through the device's
> platform data.
>
> Signed-off-by: Du, Changbin
Gah, you trapped me: you've resent it, without using the original message ID.
Too late. I'll keep the version where I've fixed
On Sun, Jul 01, 2012 at 09:53:19AM +0300, Shachar Shemesh wrote:
> From: Shachar Shemesh
>
> Commit acfa747b introduced the TTY_HUPPING flag to distinguish
> closed TTY from currently closing ones. The test in tty_set_ldisc
> still remained pointing at the old flag. This causes pppd to
>
The idea of moving rebind procedure into pm.complete
was taken from the usb-subsystem, which has similar
problems with reattaching devices during/after
resume.
Signed-off-by: Christian Lamparter
---
To Greg:
I have submitted this patch back in March and again in May.
As far as I can tell it was
Em 03-07-2012 08:19, Benoît Thébaudeau escreveu:
> Hi Changbin,
>
> On Tue, Jul 3, 2012 at 12:27:19PM +0200, Changbin Du wrote:
>> It's better to give platform code a chance to specify the allowed
>> protocols and which keymap to use.
>
> Already half done here:
>
On Thu, Jul 05, 2012 at 08:23:21PM -, Mark Brown wrote:
> wm831x devices contain a unique ID value. Feed this into the newly added
> device_add_randomness() to add some per device seed data to the pool.
>
> Signed-off-by: Mark Brown
>
> add_device_randomness() has only just been added in
On Thu, Jul 05, 2012 at 08:19:17PM -, Mark Brown wrote:
> The tamper evident features of the RTC include the "write counter" which
> is a pseudo-random number regenerated whenever we set the RTC. Since this
> value is unpredictable it should provide some useful seeding to the random
> number
This set of patches implements the core Linux support for the AArch64
(64-bit ARM) architecture.
ARM introduced AArch64 as part of the ARMv8 architecture and consists of
a substantially revised exception model (with 4 exception levels: EL0 -
user, EL1 - kernel, EL2 - hypervisor, EL3 - secure
This function reserves initial_boot_params total size and reserve map.
Signed-off-by: Catalin Marinas
Cc: Grant Likely
---
drivers/of/fdt.c | 28
include/linux/of_fdt.h |1 +
2 files changed, 29 insertions(+), 0 deletions(-)
diff --git
This patch adds support for the handling of the MMU faults (exception
entry code introduced by a previous patch) and page table management.
The user translation table is pointed to by TTBR0 and the kernel one
(swapper_pg_dir) by TTBR1. There is no translation information shared or
address space
The patch adds support for thread creation and context switching. The
context switching CPU specific code is introduced with the CPU support
patch (part of the arch/aarch64/mm/proc.S file). AArch64 supports
ASID-tagged TLBs and the ASID can be either 8 or 16-bit wide (detectable
via the
This patch adds AArch64 CPU specific functionality. It assumes that the
implementation is generic to AArch64 and does not require specific
identification. Different CPU implementations may require the setting of
various ACTLR_EL1 bits but such information is not currently available
and it should
The patch adds functionality required for cache maintenance. The AArch64
architecture mandates non-aliasing VIPT or PIPT D-cache and VIPT (may
have aliases) or ASID-tagged VIVT I-cache. Cache maintenance operations
are automatically broadcast in hardware between CPUs.
Signed-off-by: Will Deacon
This patch adds the TLB maintenance functions. There is no distinction
made between the I and D TLBs. TLB maintenance operations are
automatically broadcast between CPUs in hardware. The inner-shareable
operations are always present, even on UP systems.
NOTE: Large part of this patch to be
From: Marc Zyngier
This patch adds the support for IRQ handling. The actual interrupt
controller will be part of a separate patch (going into
drivers/irqchip/).
Signed-off-by: Marc Zyngier
Signed-off-by: Will Deacon
Signed-off-by: Catalin Marinas
---
arch/aarch64/include/asm/hardirq.h |
From: Will Deacon
The msgsnd and msgrcv system calls use size_t to represent the size of
the message being transferred. POSIX states that values of msgsz greater
than SSIZE_MAX cause the result to be implementation-defined. On Linux,
this equates to returning -EINVAL if (long) msgsz < 0.
For
From: Will Deacon
Commit 48b25c43 ("[PATCH v3] ipc: provide generic compat versions of IPC
syscalls") added a new ARCH_WANT_OLD_COMPAT_IPC config option for
architectures to select if their compat target requires the old IPC
syscall interface.
For architectures that do not require the internal
This patch introduces the atomic, mutex and futex operations. Many
atomic operations use the load-acquire and store-release operations
which imply barriers, avoiding the need for explicit DMB.
Signed-off-by: Will Deacon
Signed-off-by: Catalin Marinas
---
arch/aarch64/include/asm/atomic.h |
This patch adds support for the DMA mapping API. It uses dma_map_ops for
flexibility and it currently supports swiotlb. This patch could be
simplified further if the DMA accesses are coherent (not mandated by the
architecture) or if corresponding hooks are placed in the generic
swiotlb code to
This patch adds several definitions for device communication, including
I/O accessors and ioremap(). The __raw_* accessors are implemented as
inline asm to avoid compiler generation of post-indexed accesses (less
efficient to emulate in a virtualised environment).
Signed-off-by: Will Deacon
This patch adds SMP initialisation and spinlocks implementation for
AArch64. The spinlock support uses the new load-acquire/store-release
instructions to avoid explicit barriers. The architecture also specifies
that an event is automatically generated when clearing the exclusive
monitor state to
This adds support for setting synthetic NIC MAC address from within Linux
guests. Before using this feature, the option "spoofing of MAC address"
should be enabled at the Hyper-V manager / Settings of the synthetic
NIC.
Thanks to Kin Cho for the initial implementation and
tests. And, thanks to
This patch adds definitions for the ELF format, including personality
personality setting and EXEC_PAGESIZE. The are only two hwcap
definitions for 64-bit applications - HWCAP_FP and HWCAP_ASIMD.
Signed-off-by: Will Deacon
Signed-off-by: Catalin Marinas
---
arch/aarch64/include/asm/auxvec.h
This patch adds support for system calls coming from 64-bit
applications. It uses the asm-generic/unistd.h definitions with the
canonical set of system calls. The private system calls are only used
for 32-bit (compat) applications as 64-bit ones can set the TLS and
flush the caches entirely from
From: Will Deacon
This patch adds VDSO support for 64-bit applications. The VDSO code is
currently used for sys_rt_sigreturn() and optimised gettimeofday()
(using the user-accessible generic counter).
Signed-off-by: Will Deacon
Signed-off-by: Catalin Marinas
---
This patch adds support for signal handling. The sigreturn is done via
VDSO, introduced by a previous patch. The SA_RESTORER is still defined
as it is required for 32-bit (compat) support but it is not to be used
for 64-bit applications.
Signed-off-by: Will Deacon
Signed-off-by: Catalin Marinas
This patch add support for various user access functions. These
functions use the standard LDR/STR instructions and not the LDRT/STRT
variants in order to allow kernel addresses (after set_fs(KERNEL_DS)).
Signed-off-by: Will Deacon
Signed-off-by: Marc Zyngier
Signed-off-by: Catalin Marinas
---
1 - 100 of 500 matches
Mail list logo
