search for: irqsav

...frags += DIV_ROUND_UP(offset + len, PAGE_SIZE); > if (unlikely(frags > MAX_SKB_FRAGS + 1)) { > @@ -498,12 +499,12 @@ static int xennet_start_xmit(struct sk_buff *skb, struct net_device *dev) > goto drop; > } > > - spin_lock_irq(&np->tx_lock); > + spin_lock_irqsave(&np->tx_lock, flags); > > if (unlikely(!netif_carrier_ok(dev) || > (frags > 1 && !xennet_can_sg(dev)) || > netif_needs_gso(skb, netif_skb_features(skb)))) { > - spin_unlock_irq(&np->tx_lock); > + spin_unlock_irqrestore(&np->tx...

This got me confused for a bit while looking over this code: I had been planning on adding some blocking function calls into this function, but seeing the irqsave/irqrestore variants of spin_(un)lock() didn't make it very clear whether or not that would actually be safe. So I went ahead and reviewed every single driver in the kernel that uses this function, and they all fall into three categories: * Driver probe code * ->atomic_disable() callbacks...

An embedded and charset-unspecified text was scrubbed... Name: staging-hv-make-gvmbusconnection.channellock-a-real-spinlock.patch Url: http://lists.linux-foundation.org/pipermail/virtualization/attachments/20090717/01b2e23a/attachment.txt

An embedded and charset-unspecified text was scrubbed... Name: staging-hv-make-gvmbusconnection.channellock-a-real-spinlock.patch Url: http://lists.linux-foundation.org/pipermail/virtualization/attachments/20090717/01b2e23a/attachment.txt

...ty <avi.kivity@gmail.com> Avi Kivity <avi@redhat.com> Avik Sil <aviksil@linux.vnet.ibm.com> Bas van Sisseren <bas@quarantainenet.nl> Ben Herrenschmidt <benh@kernel.crashing.org> Benjamin Herrenschmidt <benh@kernel.crashing.org> Benoit Canet <benoit@irqsave.net> Bharat Bhushan <bharat.bhushan@freescale.com> Bharata B Rao <bharata@linux.vnet.ibm.com> Blue Swirl <blauwirbel@gmail.com> Borislav Petkov <bp@suse.de> Brad Smith <brad@comstyle.com> Bruce Rogers <brogers@suse.com> Charles Arnold <carnol...

...ty <avi.kivity@gmail.com> Avi Kivity <avi@redhat.com> Avik Sil <aviksil@linux.vnet.ibm.com> Bas van Sisseren <bas@quarantainenet.nl> Ben Herrenschmidt <benh@kernel.crashing.org> Benjamin Herrenschmidt <benh@kernel.crashing.org> Benoit Canet <benoit@irqsave.net> Bharat Bhushan <bharat.bhushan@freescale.com> Bharata B Rao <bharata@linux.vnet.ibm.com> Blue Swirl <blauwirbel@gmail.com> Borislav Petkov <bp@suse.de> Brad Smith <brad@comstyle.com> Bruce Rogers <brogers@suse.com> Charles Arnold <carnol...

...ty <avi.kivity@gmail.com> Avi Kivity <avi@redhat.com> Avik Sil <aviksil@linux.vnet.ibm.com> Bas van Sisseren <bas@quarantainenet.nl> Ben Herrenschmidt <benh@kernel.crashing.org> Benjamin Herrenschmidt <benh@kernel.crashing.org> Benoit Canet <benoit@irqsave.net> Bharat Bhushan <bharat.bhushan@freescale.com> Bharata B Rao <bharata@linux.vnet.ibm.com> Blue Swirl <blauwirbel@gmail.com> Borislav Petkov <bp@suse.de> Brad Smith <brad@comstyle.com> Bruce Rogers <brogers@suse.com> Charles Arnold <carnol...

Changes in v2: - Addressed review comments nouveau_bo_wait will make the GPU channel wait for fence if possible, otherwise falling back to waiting with the CPU using ttm_bo_wait. The nouveau_fence_sync function currently returns -ENOSYS, and is the focus of the next patch. Signed-off-by: Luca Barbieri <luca at luca-barbieri.com> --- drivers/gpu/drm/nouveau/nouveau_bo.c | 68

Nvidia released some documentation on how CRC support works on their GPUs, hooray! So: this patch series implements said CRC support in nouveau, along with adding some special debugfs interfaces for some relevant igt-gpu-tools tests (already on the ML). First - we add some new functionality to kthread_work in the kernel, and then use this to add a new feature to DRM that Ville Syrj?l? came up

The following patches introduce the core infrastructure needed to paravirtualize the 32-bit x86 Linux kernel. This is done by moving virtualization sensitive insn's or code paths to a function table, paravirt_ops. This structure can be populated with hypervisor specific calls or native stubs and currently support running on bare metal, VMI, Xen, or Lhype. These patches apply to

The following patches introduce the core infrastructure needed to paravirtualize the 32-bit x86 Linux kernel. This is done by moving virtualization sensitive insn's or code paths to a function table, paravirt_ops. This structure can be populated with hypervisor specific calls or native stubs and currently support running on bare metal, VMI, Xen, or Lhype. These patches apply to

Nvidia released some documentation on how CRC support works on their GPUs, hooray! So: this patch series implements said CRC support in nouveau, along with adding some special debugfs interfaces for some relevant igt-gpu-tools tests (already on the ML). First - we add some new functionality to kthread_work in the kernel, and then use this to add a new feature to DRM that Ville Syrj?l? came up

Hi all, First thing first: It works, I now no longer have a few dropped frames every 10s on my testbox here with the pageflip i-g-t tests. Random notes: - New design has per-crtc locks to protect the crtc input-side (pageflip, cursor) for r/w and the output state of the crtc (mode, dpms) as read-only. It also required completely revamped fb lifecycle management, those are now refcounted