On Tue, Feb 17, 2015 at 02:51:08AM -0800, Omar Sandoval wrote:
> Consider the following interleaving of overlapping calls to
> alloc_extent_buffer:
>
> Call 1:
>
> - Successfully allocates a few pages with find_or_create_page
> - find_or_create_page fails, goto free_eb
> - Unlocks the allocated
1) Missing netlink attribute validation in nft_lookup, from Patrick
McHardy.
2) Restrict ipv6 partial checksum handling to UDP, since that's the
only case it works for. From Vlad Yasevich.
3) Clear out silly device table sentinal macros used by SSB and BCMA
drivers. From Joe Perches.
On Tue, Feb 17, 2015 at 08:05:32AM -0800, Paul E. McKenney wrote:
> > FWIW, we should probably update that table to include control
> > dependencies too; we didn't (formally) have those back then I think.
> >
> > The blob under SMP BARRIER PAIRING does not mention pairing with control
> >
On Wed, Feb 4, 2015 at 6:09 AM, Quentin Lambert
wrote:
> - dev->eq_table.icm_dma = pci_map_page(dev->pdev,
> dev->eq_table.icm_page, 0,
> - PAGE_SIZE,
> PCI_DMA_BIDIRECTIONAL);
> - if (pci_dma_mapping_error(dev->pdev,
This patch adds paravirtual "devices" discovered by hv_vmbus to the
pnp layer, and adds any memory-mapped I/O space claims expressed
by those paravirtual devices to the "options" for that device in pnp.
This allows the pnp layer to choose the memory-mapped I/O space that
those paravirtual devices
On 02/16/15 21:02, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any material destined for v3.21 to your linux-next
> included trees until after v3.20-rc1 has been released.
>
> Changes since 20150216:
>
on i386, when CONFIG_IOSF_MBI=m and
CONFIG_I2C_DESIGNWARE_BAYTRAIL=y:
On 02/15/2015 01:01 AM, Raghavendra K T wrote:
> On 02/15/2015 11:25 AM, Raghavendra K T wrote:
>> Paravirt spinlock clears slowpath flag after doing unlock.
>> As explained by Linus currently it does:
>> prev = *lock;
>> add_smp(>tickets.head, TICKET_LOCK_INC);
This patch removes the code that is no longer necessary
after the first two patches in this series have been applied.
It exposed a static range of memory-mapped I/O space gleaned
from the ACPI namespace, in a way that worked for a single
paravirtual device, the video frame buffer.
Signed-off-by:
This patch adds some wrapper functions in the pnp layer. The intent is
to allow memory address space claims by devices which are descendants
(a child or grandchild of) a device which is already part of the pnp
layer. This allows a device to make a resource claim that doesn't
conflict with its
On Tue, Feb 17, 2015 at 10:01:54AM -0800, Paul E. McKenney wrote:
> > > The blob under SMP BARRIER PAIRING does not mention pairing with control
> > > dependencies; and I'm rather sure I've done so.
>
> And here is a patch for the control-dependency pairing. Thoughts?
The proposed patch does
On February 17, 2015 18:04, Sebastian Reichel wrote:
> Hi,
>
> On Mon, Feb 16, 2015 at 09:45:59PM +, Opensource [Adam Thomson] wrote:
> > Just a quick one to see what the status is on this patch set? Just
> > interested as to when it'll be pulled in.
>
> I plan to pull it into for-next once
On Tue, Feb 17, 2015 at 08:12:11AM -0600, Josh Poimboeuf wrote:
> On Tue, Feb 17, 2015 at 10:24:50AM +0100, Peter Zijlstra wrote:
> > So far stack unwinding has basically been a best effort debug output
> > kind of thing, you're wanting to make the integrity of the kernel depend
> > on it.
> >
>
On 02/17/2015 07:24 AM, Michael Mueller wrote:
> This patch implements the QMP command 'query-cpu-definitions' in the S390
> context. The command returns a in terms of machine release date descending
> sorted list of cpu model names in the current host context.
returns a list of cpu model names
On Sun, Feb 15, 2015 at 11:40:06PM +0100, Pavel Machek wrote:
> > So keeping that much memory pinned in the kernel when I can prove it
> > is uncessary for my system (either because there is no suspend/resume
> > possibility, or because I know the CPU can always access the
> > filesytem) is very
Hi,
On Mon, Feb 16, 2015 at 09:45:59PM +, Opensource [Adam Thomson] wrote:
> Just a quick one to see what the status is on this patch set? Just
> interested as to when it'll be pulled in.
I plan to pull it into for-next once -rc1 has been tagged (probably
about a week). Feel free to send a
On 02/17/2015 07:24 AM, Michael Mueller wrote:
> This patch implements a new QMP request named 'query-cpu-model'.
> It returns the cpu model of cpu 0 and its backing accelerator.
>
> request:
> {"execute" : "query-cpu-model" }
>
> answer:
> {"return" : {"name": "2827-ga2", "accelerator":
On Tue, Feb 17, 2015 at 08:05:32AM -0800, Paul E. McKenney wrote:
> On Tue, Feb 17, 2015 at 02:05:23PM +0100, Peter Zijlstra wrote:
> > On Tue, Feb 17, 2015 at 01:12:58PM +0100, Peter Zijlstra wrote:
> > > --- a/kernel/sched/core.c
> > > +++ b/kernel/sched/core.c
> > > @@ -341,6 +341,22 @@ static
On Tue, Feb 17, 2015 at 9:41 AM, Linus Torvalds
wrote:
> On Tue, Feb 17, 2015 at 12:33 AM, Olof Johansson wrote:
>>
>> Conflicts:
>>
>> arch/arm/boot/dts/rk3288.dtsi: add/add: Keep both sides
> ...
>
> You mixed up the aliases of this pull and the previous DT pull.
>
> Not a real problem, but
* Sebastian Andrzej Siewior | 2015-02-17 18:53:17 [+0100]:
>* Purcareata Bogdan | 2015-02-17 14:27:44 [+0200]:
>
>>Ping?
>>
>>On 02.02.2015 11:35, Purcareata Bogdan wrote:
>>>Ping?
>
>No body?
bah! That mutt thing is too fast.
The raw conversation looks sane and could go upstream. This other
On Tue, 17 Feb 2015 12:10:17 -0500
"J. Bruce Fields" wrote:
> On Tue, Feb 17, 2015 at 07:46:28AM -0500, Jeff Layton wrote:
> > As Linus pointed out:
> >
> > Say we have an existing flock, and now do a new one that conflicts. I
> > see what looks like three separate bugs.
> >
> > -
On Tue, 17 Feb 2015, Lorenzo Pieralisi wrote:
> On Mon, Feb 16, 2015 at 12:15:09PM +, Peter Zijlstra wrote:
> > From: Thomas Gleixner
> >
> > This function is intended to use by the freezer once the freezer folks
> > solved their race issues. Also required to get rid of the ARM BL
> >
* Purcareata Bogdan | 2015-02-17 14:27:44 [+0200]:
>Ping?
>
>On 02.02.2015 11:35, Purcareata Bogdan wrote:
>>Ping?
No body?
Sebatian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On Sat, 2015-02-14 at 06:25 +, Deucher, Alexander wrote:
> > -Original Message-
> > From: Ross Zwisler [mailto:ross.zwis...@linux.intel.com]
> > Sent: Friday, February 13, 2015 10:55 PM
> > To: Michel Dänzer
> > Cc: linux-kernel@vger.kernel.org; dri-de...@lists.freedesktop.org;
* Peter Zijlstra | 2015-01-21 16:07:16 [+0100]:
>On Tue, Jan 20, 2015 at 01:16:13PM -0500, Steven Rostedt wrote:
>> I'm actually wondering if we should just nuke the _interruptible()
>> version of swait. As it should only be all interruptible or all not
>> interruptible, that the swait_wake()
Lazytime stuff from tytso. Please, pull from
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git lazytime.
Shortlog:
Theodore Ts'o (3):
vfs: add support for a lazytime mount option
vfs: add find_inode_nowait() function
ext4: add optimization for the lazytime
On Tue, Feb 17, 2015 at 12:33 AM, Olof Johansson wrote:
>
> Conflicts:
>
> arch/arm/boot/dts/rk3288.dtsi: add/add: Keep both sides
...
You mixed up the aliases of this pull and the previous DT pull.
Not a real problem, but while resolving the DT aliases (which you
claimed had "No conflicts") I
More iov_iter work - missing counterpart of iov_iter_init() for
bvec-backed ones and vfs_read_iter()/vfs_write_iter() - wrappers for
sync calls of ->read_iter()/->write_iter().
Please, pull from
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git iov_iter
Shortlog:
Al Viro (1):
On Tue, 17 Feb 2015, Lee Jones wrote:
> Arnd, Greg,
>
> Perhaps you have some ideas WRT programmables (PLDs/CPLDs/FPGAs)?
FWIW...
The Lubbock is an ancient development board (circa 2003) using a CPLD to
multiplex a couple things on the board. I really doubt anyone would
reprogram this
Rework of getname/getname_kernel/etc., mostly from Paul Moore.
Gets rid of quite a pile of kludges between namei and audit...
Please, pull from
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git getname2
Shortlog:
Al Viro (2):
cut down the number of do_path_lookup() callers
On Tue, Feb 17, 2015 at 05:13:19PM +, Stathis Voukelatos wrote:
> Hi Mark,
>
> On 17/02/15 16:35, Mark Rutland wrote:
> >
> +- tstamp-hz : frequency of the timestamp counter
> >
> > Is this the frequency the clock is running at, or a frequency that it
> > should be programmed to in order
On Tuesday, February 17, 2015 01:29:10 PM Preeti U Murthy wrote:
> Hi Rafael,
Hi,
> Can you please pull this patch ?
Sorry, I wasn't sure whether or not the patch was for me to take and then
I've been traveling lately. Applied now.
> Another patch based on top of this is waiting to be pulled:
On Monday, February 16, 2015 08:36:37 PM Pavel Machek wrote:
> On Mon 2015-02-16 10:11:13, Jiang Liu wrote:
> > Commit b568b8601f05 ("Treat SCI interrupt as normal GSI interrupt")
> > accidently removes support of legacy PIC interrupt when fixing a
>
> accidentaly?
>
> > regression for Xen,
On Tue, Feb 17, 2015 at 10:56 AM, Harish Jenny K N
wrote:
> usecase: two sd cards are being mounted in parallel at same time on
> dual core. example modules which are getting loaded is nls_cp437.
> While one module is being loaded , it starts creating sysfs files.
> meanwhile on other core,
Next pile: debugfs patches, mostly to make it possible for something
like tracefs to be transparently automounted on given directory in debugfs.
New primitive in there is debugfs_create_automount(name, parent, func, arg),
which creates a directory and makes its ->d_automount() return
* Marcelo Tosatti | 2015-01-26 19:12:31 [-0200]:
>Ping ?
please resent.
Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the
On 02/17/2015 02:07 PM, Robert Jarzmik wrote:
> Maxime Ripard writes:
>
>> On Mon, Feb 16, 2015 at 10:36:02PM +0100, Robert Jarzmik wrote:
>>> diff --git a/drivers/mtd/nand/pxa3xx_nand.c b/drivers/mtd/nand/pxa3xx_nand.c
>>> index e512902..6e569e9 100644
>>> --- a/drivers/mtd/nand/pxa3xx_nand.c
On Tue, Feb 17, 2015 at 04:02:21PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any material destined for v3.21 to your linux-next
> included trees until after v3.20-rc1 has been released.
>
> Changes since 20150216:
>
> The slave-dma tree lost its build failure.
>
>
This cycle a lot of stuff sits on topical branches, so I'll be
sending more or a less pull request per branch. If you prefer a single
pull request in such situations for the future, please tell. This is
the first pile; more to follow in a few. In this one are several misc
commits from
The commit "drm/exynos: remove exynos_plane_dpms" (d9ea6256) removed the
use of the enabled flag, which means that the code may attempt to call
win_enable on a NULL crtc. This results in the following oops on
Arndale:
[1.673479] Unable to handle kernel NULL pointer dereference at virtual
Removing myself as a co-maintainer.
Signed-off-by: Matt Porter
---
MAINTAINERS | 1 -
1 file changed, 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 2ebb056..e21438b 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2077,7 +2077,6 @@ F:drivers/net/ethernet/broadcom/bnx2x/
On Tue, Feb 17, 2015 at 07:46:28AM -0500, Jeff Layton wrote:
> As Linus pointed out:
>
> Say we have an existing flock, and now do a new one that conflicts. I
> see what looks like three separate bugs.
>
> - We go through the first loop, find a lock of another type, and
> delete
Hi Mark,
On 17/02/15 16:35, Mark Rutland wrote:
+- tstamp-hz : frequency of the timestamp counter
Is this the frequency the clock is running at, or a frequency that it
should be programmed to in order to be used?
The former can be queried from the common clock framework, and if you
Yes suggested code modification will break if (p==d) branch is not taken.
Thanks for pointing out this point.
So its better to keep code as it is.
On Tue, Feb 17, 2015 at 12:44 AM, Richard Weinberger
wrote:
> On Mon, Feb 16, 2015 at 7:49 PM, Anshul Garg wrote:
>> From: Anshul Garg
>>
>>
On 17/02/2015 16:02, Igor Mammedov wrote:
>> >
>> > Not if there are about 6 regions, I think.
> When memslots where increased to 509 and look up of them was replaced on
> binary search results were on par with linear search for a default 13
> memslots VM.
>
> Adding LRU
You mean MRU. :)
>
On 02/17/2015 03:34 AM, Jiri Slaby wrote:
This is the start of the stable review cycle for the 3.12.38 release.
There are 122 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by
On 02/15/2015 04:40 PM, Pavel Machek wrote:
> On Wed 2015-01-21 13:27:00, Jason Gunthorpe wrote:
>> On Wed, Jan 21, 2015 at 06:33:12PM +0200, Pantelis Antoniou wrote:
>> My point is that the current firmware layer is overly cautious and
>> FPGAs are very big. My current project on small Xilinx
Maxime Ripard writes:
> On Mon, Feb 16, 2015 at 10:36:02PM +0100, Robert Jarzmik wrote:
>> diff --git a/drivers/mtd/nand/pxa3xx_nand.c b/drivers/mtd/nand/pxa3xx_nand.c
>> index e512902..6e569e9 100644
>> --- a/drivers/mtd/nand/pxa3xx_nand.c
>> +++ b/drivers/mtd/nand/pxa3xx_nand.c
>> @@ -576,11
This reverts commit 8dcc14f82f06fce997e35f4c77ced9d4ed192f31.
This patch causes this error on Arndale:
[1.643800] kernel BUG at drivers/iommu/exynos-iommu.c:481!
[1.649355] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM
[1.655170] Modules linked in:
[1.658203] CPU: 1 PID: 1
On Mon, Feb 16, 2015 at 7:46 PM, Ben Hutchings wrote:
> 3.2.67-rc1 review patch. If anyone has any objections, please let me know.
No objections, but I think you want 06cf35f903aa ("PCI: Handle
read-only BARs on AMD CS553x devices") at the same time.
> --
>
> From: Myron Stowe
On 2/15/2015 7:33 AM, Mans Rullgard wrote:
> If a mux clock is initialised (by hardware or firmware) with an
> invalid parent, its ->get_parent() can return an out of range
> index. For example, the generic mux clock attempts to return
> -EINVAL, which due to the u8 return type ends up a rather
On Tue, Feb 17, 2015 at 4:39 AM, Borislav Petkov wrote:
> On Tue, Feb 17, 2015 at 01:21:20PM +0100, Jiri Kosina wrote:
>> I don't have strong feelings either way. It seems slightly nicer
>> to have a predictable oops output format no matter the CONFIG_
>> options and command-line contents, but if
The hpsa driver carries a more recent version,
copy the table from there.
Signed-off-by: Tomas Henzl
---
drivers/block/cciss.c | 23 +--
1 file changed, 21 insertions(+), 2 deletions(-)
diff --git a/drivers/block/cciss.c b/drivers/block/cciss.c
index 48498220cd..0ca65b25ef
and devices not supported by this driver from unresettable list
Signed-off-by: Tomas Henzl
---
drivers/block/cciss.c | 4
1 file changed, 4 deletions(-)
diff --git a/drivers/block/cciss.c b/drivers/block/cciss.c
index ff20f192b0..48498220cd 100644
--- a/drivers/block/cciss.c
+++
On Tue, 17 Feb 2015, Josh Poimboeuf wrote:
> On Mon, Feb 16, 2015 at 05:06:15PM +0100, Miroslav Benes wrote:
> > On Fri, 13 Feb 2015, Josh Poimboeuf wrote:
> >
> > > On Fri, Feb 13, 2015 at 05:17:10PM +0100, Miroslav Benes wrote:
> > > > On Fri, 13 Feb 2015, Josh Poimboeuf wrote:
> > > > > Hm,
On Tue, Feb 17, 2015 at 04:22:04PM +, Stathis Voukelatos wrote:
> Hi Mark,
>
> On 17/02/15 14:51, Mark Rutland wrote:
>
> >> +Matched packet bytes and timestamp values are returned through a
> >> +FIFO. Timestamps are provided to the module through an externally
> >> +generated Gray-encoded
Hi Mark,
On 17/02/15 14:51, Mark Rutland wrote:
+Matched packet bytes and timestamp values are returned through a
+FIFO. Timestamps are provided to the module through an externally
+generated Gray-encoded counter.
Does this counter unit need to be enabled (or have any input clocks
enabled)?
Hi Stefan,
On Sat, Jan 31, 2015 at 12:53:46AM +0100, Stefan Agner wrote:
> On the Vybrid platform this did not lead to CPU faults (so far),
> but is_smp checks evaluate to true which is not optimal
> performance wise.
Just curious, was the performance difference considerable ?
Regards
Afzal
--
This is on a Haswell machine, current git as of this past Friday.
I let the perf_fuzzer run and it took 4 days to find this.
Sadly it doesn't seem to be reproducible so I am not sure
how it exactly got into this state.
It got stuck and kept printing the following message until I rebooted
the
On 2/17/15 1:20 AM, Andrey Vagin wrote:
And here are statistics about syscalls which were called by each
command.
$ perf stat -e syscalls:sys_exit* -- ps ax -o pid,ppid 2>&1 | grep syscalls |
sort -n -r | head -n 5
20,713 syscalls:sys_exit_open
20,710
On Tue, Feb 17, 2015 at 02:05:23PM +0100, Peter Zijlstra wrote:
> On Tue, Feb 17, 2015 at 01:12:58PM +0100, Peter Zijlstra wrote:
> > --- a/kernel/sched/core.c
> > +++ b/kernel/sched/core.c
> > @@ -341,6 +341,22 @@ static struct rq *task_rq_lock(struct ta
> >
On Tue, Feb 17, 2015 at 04:48:39PM +0100, Miroslav Benes wrote:
> On Tue, 17 Feb 2015, Josh Poimboeuf wrote:
>
> > On Mon, Feb 16, 2015 at 03:19:10PM +0100, Miroslav Benes wrote:
> > > On Mon, 9 Feb 2015, Josh Poimboeuf wrote:
> > >
>
> [...]
>
> > > > +
> > > > +void
On Tue, 17 Feb 2015, Joonsoo Kim wrote:
> Hmm...so far, SLAB focus on temporal locality rather than spatial locality
> as you know. Why SLAB need to consider spatial locality first in this
> kmem_cache_alloc_array() case?
Well we are talking about a large number of objects. And going around
This soft reset used to be located after the register patch had been
applied, but has since moved to before the patch is applied. At the new
location there is no requirement to do a register sync as no register
writes will have happened yet.
Signed-off-by: Charles Keepax
---
On Mon, Feb 16, 2015 at 05:06:15PM +0100, Miroslav Benes wrote:
> On Fri, 13 Feb 2015, Josh Poimboeuf wrote:
>
> > On Fri, Feb 13, 2015 at 05:17:10PM +0100, Miroslav Benes wrote:
> > > On Fri, 13 Feb 2015, Josh Poimboeuf wrote:
> > > > Hm, even with Jiri Slaby's suggested fix to add the
On Tue, 2015-02-17 at 13:33 +0300, Alexander Drozdov wrote:
> skb_copy_bits() returns zero on success and negative value on error,
> so it is needed to invert the condition in ip_check_defrag().
>
> Fixes: 1bf3751ec90c ("ipv4: ip_check_defrag must not modify skb before
> unsharing")
>
On Tue, 17 Feb 2015, Josh Poimboeuf wrote:
> On Mon, Feb 16, 2015 at 03:19:10PM +0100, Miroslav Benes wrote:
> > On Mon, 9 Feb 2015, Josh Poimboeuf wrote:
> >
[...]
> > > +
> > > +void klp_unpatch_objects(struct klp_patch *patch)
> > > +{
> > > + struct klp_object *obj;
> > > +
> > > + for
On Monday, February 16, 2015 11:33:46 PM Ameen Ali wrote:
> Fixed a coding style issue (unnecessary parentheses , unnecessary braces)
>
> Signed-off-by: Ameen-Ali
> ---
> kernel/audit.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
Merged into my next-queue branch, I'll push to
With task_blocks_on_rt_mutex() returning early -EDEADLK we never add the
waiter to the waitqueue. Later, we try to remove it via remove_waiter()
and go boom in rt_mutex_top_waiter() because rb_entry() gives a NULL
pointer.
Tested on v3.18-RT where rtmutex is used for regular mutex and I tried
to
> -Original Message-
> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]
> Sent: Tuesday, February 17, 2015 7:20 AM
> To: KY Srinivasan; de...@linuxdriverproject.org
> Cc: Haiyang Zhang; linux-kernel@vger.kernel.org; Dexuan Cui
> Subject: [PATCH] Drivers: hv: hv_balloon: eliminate the
When many memory regions are being added and automatically onlined the
following lockup is sometimes observed:
INFO: task udevd:1872 blocked for more than 120 seconds.
...
Call Trace:
[] schedule_timeout+0x22c/0x350
[] wait_for_common+0x10f/0x160
[] ? default_wake_function+0x0/0x20
[]
in today's linux-next
(next-20150217).
Yes.
That commit removed the Kconfig symbol HPUX. As a result BINFMT_SOM (see
fs/Kconfig.binfmt) can't be set anymore. I assume a patch to remove that
symbol too is also part of that series. Is that correct?
I missed it, but just sent out a patch to remove
On Sat, Feb 14, 2015 at 12:40:01PM +0100, Jiri Slaby wrote:
> On 02/09/2015, 06:31 PM, Josh Poimboeuf wrote:
> > Add a basic per-task consistency model. This is the foundation which
> > will eventually enable us to patch those ~10% of security patches which
> > change function prototypes and/or
On 02/17/2015 03:35 PM, Sakari Ailus wrote:
Jacek Anaszewski wrote:
On 02/17/2015 03:06 PM, Sakari Ailus wrote:
Hi Jacek,
Jacek Anaszewski wrote:
Hi Hans, Sakari,
On 02/17/2015 12:32 PM, Sakari Ailus wrote:
Hi Hans,
Hans Verkuil wrote:
...
Unfortunately, it only works one time, because
Volatile variables are also writable now. Update the documentation
accordingly.
Acked-by: Hans Verkuil
Signed-off-by: Ricardo Ribalda Delgado
---
v4: Hans Verkuil:
Fix typos and add ack-by Hans
Documentation/DocBook/media/v4l/vidioc-dqevent.xml | 7 ---
On Tue, Feb 17, 2015 at 09:00:47AM -0600, Rob Herring wrote:
> +GregKH
>
> On Sun, Feb 15, 2015 at 9:59 PM, Benjamin Herrenschmidt
> wrote:
> > So I've been annoyed lately with having a bunch of devices such as i2c
> > eeproms (for use by VPDs, server world !) and other bits and pieces that
> >
On Mon, Feb 16, 2015 at 03:19:10PM +0100, Miroslav Benes wrote:
> On Mon, 9 Feb 2015, Josh Poimboeuf wrote:
>
> > Add a basic per-task consistency model. This is the foundation which
> > will eventually enable us to patch those ~10% of security patches which
> > change function prototypes and/or
Volatile controls can change their value outside the v4l-ctrl framework.
We should ignore the cached written value of the ctrl when evaluating if
we should run s_ctrl.
Signed-off-by: Ricardo Ribalda Delgado
---
v4: Hans Verkuil:
explicity set has_changed to false. and add comment
On 02/15/2015 11:54 PM, Hiroshi Shimamoto wrote:
>>> Can you please fix up your patches based on my tree:
>>> git://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/que
>>> ue.git
>>
>> Yes. I haven't noticed your tree.
>> Will resend patches against
+GregKH
On Sun, Feb 15, 2015 at 9:59 PM, Benjamin Herrenschmidt
wrote:
> So I've been annoyed lately with having a bunch of devices such as i2c
> eeproms (for use by VPDs, server world !) and other bits and pieces that
> I want to be able to identify from userspace, and possibly provide
>
On Tue, 17 Feb 2015 14:29:31 +0100
"Michael S. Tsirkin" wrote:
> On Tue, Feb 17, 2015 at 02:11:37PM +0100, Paolo Bonzini wrote:
> >
> >
> > On 17/02/2015 13:32, Michael S. Tsirkin wrote:
> > > On Tue, Feb 17, 2015 at 11:59:48AM +0100, Paolo Bonzini wrote:
> > >>
> > >>
> > >> On 17/02/2015
On 02/17/2015 04:34 AM, Jiri Slaby wrote:
> This is the start of the stable review cycle for the 3.12.38 release.
> There are 122 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should
On Mon, Feb 16, 2015 at 11:16:11AM +0100, Jiri Slaby wrote:
> On 02/09/2015, 06:31 PM, Josh Poimboeuf wrote:
> > Update a tasks's universe when returning from a system call or user
> > space interrupt, or after handling a signal.
> >
> > This greatly increases the chances of a patch operation
On 02/17/2015 03:41 PM, Ricardo Ribalda Delgado wrote:
> Volatile variables are also writable now. Update the documentation
> accordingly.
>
> Signed-off-by: Ricardo Ribalda Delgado
> ---
> Documentation/DocBook/media/v4l/vidioc-dqevent.xml | 7 ---
>
On Tue, Feb 17, 2015 at 02:03:31PM +, Stathis Voukelatos wrote:
> Signed-off-by: Stathis Voukelatos
> ---
> .../bindings/net/linn-ether-packet-sniffer.txt | 42
> ++
> .../devicetree/bindings/vendor-prefixes.txt| 1 +
> 2 files changed, 43 insertions(+)
>
On 02/17/2015 03:41 PM, Ricardo Ribalda Delgado wrote:
> Volatile controls can change their value outside the v4l-ctrl framework.
> We should ignore the cached written value of the ctrl when evaluating if
> we should run s_ctrl.
>
> Signed-off-by: Ricardo Ribalda Delgado
> ---
>
On Tue, Feb 17, 2015 at 10:06:07AM +, David Laight wrote:
> From: Greg KH
> > > + for (i = 0 ; i < urb->actual_length ; i += 2) {
> > > + tty_flag = TTY_NORMAL;
> > > +
> > > + if (unlikely(data[i+0] & UART_LSR_BRK_ERROR_BITS)) {
> >
> > Never use unlikely() unless you can
This is v3 of the patch.
I forgot to add it to the subject. I have marked v1 and v2 as
Superseded on patchwork
Thanks
On Tue, Feb 17, 2015 at 3:41 PM, Ricardo Ribalda Delgado
wrote:
> Volatile controls can change their value outside the v4l-ctrl framework.
> We should ignore the cached written
On 17/02/2015 15:44, Igor Mammedov wrote:
> As alternative:
> we can filter out hotplugged memory and vhost will continue to work with
> only initial memory.
> So question is id we have to tell vhost about hotplugged memory?
Yes, I think so.
Paolo
--
To unsubscribe from this list: send the
On Tue, 17 Feb 2015 13:32:12 +0100
"Michael S. Tsirkin" wrote:
> On Tue, Feb 17, 2015 at 11:59:48AM +0100, Paolo Bonzini wrote:
> >
> >
> > On 17/02/2015 10:02, Michael S. Tsirkin wrote:
> > > > Increasing VHOST_MEMORY_MAX_NREGIONS from 65 to 509
> > > > to match KVM_USER_MEM_SLOTS fixes issue
Hello Sakari
On Tue, Feb 17, 2015 at 1:47 PM, Sakari Ailus
wrote:
> Hi Ricardo,
>
> Thanks for the patch!
Thank you
>
>
> Acked-by: Sakari Ailus
Could you take a look to v3 of the patch
Thanks!
>
> --
> Sakari Ailus
> sakari.ai...@linux.intel.com
--
Ricardo Ribalda
--
To unsubscribe
Volatile variables are also writable now. Update the documentation
accordingly.
Signed-off-by: Ricardo Ribalda Delgado
---
Documentation/DocBook/media/v4l/vidioc-dqevent.xml | 7 ---
Documentation/DocBook/media/v4l/vidioc-queryctrl.xml | 6 --
Volatile controls can change their value outside the v4l-ctrl framework.
We should ignore the cached written value of the ctrl when evaluating if
we should run s_ctrl.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/media/v4l2-core/v4l2-ctrls.c | 6 ++
1 file changed, 6 insertions(+)
With this commit, the LSM Smack implements the LSM
side part of the system call keyctl with the action
code KEYCTL_GET_SECURITY.
It is now possible to get the context of, for example,
the user session key using the command "keyctl security @s".
Signed-off-by: José Bollo
---
Jacek Anaszewski wrote:
> On 02/17/2015 03:06 PM, Sakari Ailus wrote:
>> Hi Jacek,
>>
>> Jacek Anaszewski wrote:
>>> Hi Hans, Sakari,
>>>
>>> On 02/17/2015 12:32 PM, Sakari Ailus wrote:
Hi Hans,
Hans Verkuil wrote:
...
>> Unfortunately, it only works one time, because the
On Mon, Feb 16, 2015 at 12:15:09PM +, Peter Zijlstra wrote:
> From: Thomas Gleixner
>
> This function is intended to use by the freezer once the freezer folks
> solved their race issues. Also required to get rid of the ARM BL
> switcher tick hackery.
Totally agree with the patch(es), but I
This patch introduces the function cpu_desc_avail() which returns by
default true if not architecture specific implemented. Its intention
is to indicate if the cpu model description is available for display
by list_cpus(). This change allows cpu model descriptions to become
dynamically created by
This patch provides routines to dynamically update the previously defined
S390 cpu classes in the current host context. The main function performing
this process is s390_setup_cpu_classes(). It takes the current host context
as parameter to setup the classes accordingly. It basically performs the
This patch set in combination with its kernel kvm patch set proposes an
implementation of S390 cpu models. The origin of this item is to provide
a means for management interfaces like libvirt to draw decisions if life
guest migration to a target hypervisor is reasonable.
A migration constraint is
This patch implements a new QMP request named 'query-cpu-model'.
It returns the cpu model of cpu 0 and its backing accelerator.
request:
{"execute" : "query-cpu-model" }
answer:
{"return" : {"name": "2827-ga2", "accelerator": "kvm" }}
Alias names are resolved to their respective machine
Signed-off-by: Michael Mueller
---
linux-headers/asm-s390/kvm.h | 20
1 file changed, 20 insertions(+)
diff --git a/linux-headers/asm-s390/kvm.h b/linux-headers/asm-s390/kvm.h
index d36b2fa..e38c942 100644
--- a/linux-headers/asm-s390/kvm.h
+++
301 - 400 of 1458 matches
Mail list logo
