Hi Gavin,
On 2016/7/1 10:25, Gavin Shan wrote:
On Thu, Jun 30, 2016 at 06:53:10PM +0800, Yongji Xie wrote:
When using resource_alignment kernel parameter, the current
implement reassigns the alignment by changing resources' size
which can potentially break some drivers. For example, the driver
Hi Gavin,
On 2016/7/1 14:05, Gavin Shan wrote:
On Fri, Jul 01, 2016 at 01:27:17PM +0800, Yongji Xie wrote:
On Thu, Jun 30, 2016 at 06:53:08PM +0800, Yongji Xie wrote:
VF BARs are read-only zeroes according to SRIOV spec,
the normal way(writing BARs) of allocating resources wouldn't
be applied
Am 30.06.2016 um 21:05 schrieb Jonathan Corbet :
> On Thu, 30 Jun 2016 14:00:21 +0200
> Markus Heiser wrote:
>
>> this is my flat-table patch on top of your docs-next branch / we discussed on
>> the ML
>
> Hmm... we don't have an official kernel coding style for Python, but if
> we did, I'd s
On Fri, Jul 01, 2016 at 01:27:17PM +0800, Yongji Xie wrote:
>>On Thu, Jun 30, 2016 at 06:53:08PM +0800, Yongji Xie wrote:
>>>VF BARs are read-only zeroes according to SRIOV spec,
>>>the normal way(writing BARs) of allocating resources wouldn't
>>>be applied to VFs. The VFs' resources would be alloc
Hi Gavin,
On 2016/7/1 8:39, Gavin Shan wrote:
On Thu, Jun 30, 2016 at 06:53:08PM +0800, Yongji Xie wrote:
VF BARs are read-only zeroes according to SRIOV spec,
the normal way(writing BARs) of allocating resources wouldn't
be applied to VFs. The VFs' resources would be allocated
when we enable
Hi Gavin,
On 2016/7/1 8:28, Gavin Shan wrote:
On Thu, Jun 30, 2016 at 06:53:07PM +0800, Yongji Xie wrote:
PCI resources allocator will use firmware setup and not try to
reassign resource when PCI_PROBE_ONLY or IORESOURCE_PCI_FIXED
is set.
The enforced alignment in pci_reassigndev_resource_ali
On Thu, Jun 30, 2016 at 06:53:10PM +0800, Yongji Xie wrote:
>When using resource_alignment kernel parameter, the current
>implement reassigns the alignment by changing resources' size
>which can potentially break some drivers. For example, the driver
>uses the size to locate some register whose len
This patch fix some spelling typo found in
Documentation/x86.
Signed-off-by: Masanari Iida
---
Documentation/x86/intel_mpx.txt | 6 +++---
Documentation/x86/tlb.txt | 4 ++--
Documentation/x86/x86_64/machinecheck | 2 +-
3 files changed, 6 insertions(+), 6 deletions(-)
diff --
On Thu, Jun 30, 2016 at 06:53:11PM +0800, Yongji Xie wrote:
>Now we use the IORESOURCE_STARTALIGN to identify bridge resources
>in __assign_resources_sorted(). That's quite fragile. We may also
>set flag IORESOURCE_STARTALIGN for SR-IOV resources in some cases,
>for example, using the option "nores
On Thu, Jun 30, 2016 at 06:53:09PM +0800, Yongji Xie wrote:
>We should not disable memory decoding when we reassign alignment
>in pci_reassigndev_resource_alignment(). It's meaningless and
>have some side effect. For example, some fixup functions such as
>quirk_e100_interrupt() read PCI_COMMAND_MEM
On Thu, Jun 30, 2016 at 06:53:08PM +0800, Yongji Xie wrote:
>VF BARs are read-only zeroes according to SRIOV spec,
>the normal way(writing BARs) of allocating resources wouldn't
>be applied to VFs. The VFs' resources would be allocated
>when we enable SR-IOV capability. So we should not try to
>rea
On Thu, Jun 30, 2016 at 06:53:07PM +0800, Yongji Xie wrote:
>PCI resources allocator will use firmware setup and not try to
>reassign resource when PCI_PROBE_ONLY or IORESOURCE_PCI_FIXED
>is set.
>
>The enforced alignment in pci_reassigndev_resource_alignment()
>should be ignored in this case. Othe
On Fri, Jun 24, 2016 at 01:40:41PM -0700, Andy Lutomirski wrote:
> On Fri, Jun 24, 2016 at 12:04 PM, Kees Cook wrote:
> > On Fri, Jun 24, 2016 at 9:02 AM, Jason Cooper wrote:
> >> Thomas,
> >>
> >> Sorry for wandering off the topic of your series. The big take away for
> >> me is that you and Ke
Hi Kees,
On Fri, Jun 24, 2016 at 12:04:32PM -0700, Kees Cook wrote:
> On Fri, Jun 24, 2016 at 9:02 AM, Jason Cooper wrote:
> > Thomas,
> >
> > Sorry for wandering off the topic of your series. The big take away for
> > me is that you and Kees are concerned about x86 systems pre-RDRAND.
> > Just
Em Thu, 30 Jun 2016 13:05:11 -0600
Jonathan Corbet escreveu:
> Anyway, I don't want to delay this work, so I have gone ahead and applied
> it;
Got already one issue... Maybe on Jeni's changes to the makefiles...
I want to be able to compile just the book I'm working. Using the usual
syntax to
Hi Markus/Jon,
Em Thu, 30 Jun 2016 13:05:11 -0600
Jonathan Corbet escreveu:
> On Thu, 30 Jun 2016 14:00:21 +0200
> Markus Heiser wrote:
>
> > this is my flat-table patch on top of your docs-next branch / we discussed
> > on
> > the ML
>
> Hmm... we don't have an official kernel coding st
On Thu, 30 Jun 2016 14:00:21 +0200
Markus Heiser wrote:
> this is my flat-table patch on top of your docs-next branch / we discussed on
> the ML
Hmm... we don't have an official kernel coding style for Python, but if
we did, I'd sure like it to be a lot more like the usual Python
conventions.
On Wed, 29 Jun 2016 18:05:56 +0900
Masanari Iida wrote:
> This patch fix a spelling typo in intel_powerclamp.txt
Applied to the docs tree, thanks.
jon
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majord...@vger.kernel.org
More majordomo inf
Hi Mauro,
this is the reST migration of the *media* DocBook-XML set [1]. Its
based on your:
https://git.linuxtv.org/mchehab/experimental.git mchehab/docs-next
Since the flat-table patch is not yet in Jon's docs-next and your
mchehab/docs-next is one behind Jon', I had to merge these patches.
Implements the reST flat-table directive.
The ``flat-table`` is a double-stage list similar to the ``list-table`` with
some additional features:
* column-span: with the role ``cspan`` a cell can be extended through
additional columns
* row-span: with the role ``rspan`` a cell can be extended t
Hi Jonathan,
this is my flat-table patch on top of your docs-next branch / we discussed on
the ML[1]
[1] http://mid.gmane.org/573d454c-2f55-4dd7-9c16-00b3897ae...@darmarit.de
Markus Heiser (1):
doc-rst: flat-table directive - initial implementation
Documentation/conf.py |
PCI resources allocator will use firmware setup and not try to
reassign resource when PCI_PROBE_ONLY or IORESOURCE_PCI_FIXED
is set.
The enforced alignment in pci_reassigndev_resource_alignment()
should be ignored in this case. Otherwise, some PCI devices'
resources would be released here and not
VF BARs are read-only zeroes according to SRIOV spec,
the normal way(writing BARs) of allocating resources wouldn't
be applied to VFs. The VFs' resources would be allocated
when we enable SR-IOV capability. So we should not try to
reassign alignment after we enable VFs. It's meaningless
and will re
Now we use the IORESOURCE_STARTALIGN to identify bridge resources
in __assign_resources_sorted(). That's quite fragile. We may also
set flag IORESOURCE_STARTALIGN for SR-IOV resources in some cases,
for example, using the option "noresize" of parameter
"pci=resource_alignment".
In this patch, we t
When using resource_alignment kernel parameter, the current
implement reassigns the alignment by changing resources' size
which can potentially break some drivers. For example, the driver
uses the size to locate some register whose length is related
to the size.
This patch adds a new option "nores
When vfio passthrough a PCI device of which MMIO BARs are
smaller than PAGE_SIZE, guest will not handle the mmio
accesses to the BARs which leads to mmio emulations in host.
This is because vfio will not allow to passthrough one BAR's
mmio page which may be shared with other BARs. Otherwise,
there
We should not disable memory decoding when we reassign alignment
in pci_reassigndev_resource_alignment(). It's meaningless and
have some side effect. For example, some fixup functions such as
quirk_e100_interrupt() read PCI_COMMAND_MEMORY to know whether
the devices has been initialized by the firm
This series aims to add an option for PCI resource allocator to
force BARs not to share PAGE_SIZE. This would make sense to VFIO
driver. Because current VFIO implementation disallows to mmap
sub-page(size < PAGE_SIZE) MMIO BARs which may share the same page
with other BARs for security reasons
Now we can use something like "pci=resource_alignment=*:*:*.*:noresize"
to enforce the alignment of all MMIO BARs to be at least PAGE_SIZE so
that we can passthrough sub-page(size < PAGE_SIZE) BARs to guest in
VFIO module.
But sometimes we may want to enable this feature by default on
some platfor
Em Thu, 30 Jun 2016 11:25:11 +0200
Markus Heiser escreveu:
> Am 29.06.2016 um 22:57 schrieb Mauro Carvalho Chehab
> :
>
> > Em Wed, 29 Jun 2016 11:52:09 -0600
> > Jonathan Corbet escreveu:
> >
> >>> 2. What is the best way to ship these migrations
> >>>
> >>> or better I asked, what is you
Am 29.06.2016 um 22:57 schrieb Mauro Carvalho Chehab :
> Em Wed, 29 Jun 2016 11:52:09 -0600
> Jonathan Corbet escreveu:
>
>>> 2. What is the best way to ship these migrations
>>>
>>> or better I asked, what is your recommendation for a
>>> migration strategy. Jani says, that this better belong
On 13 April 2016 at 20:15, Emil Velikov wrote:
> Hi Xinliang,
>
> On 11 April 2016 at 09:55, Xinliang Liu wrote:
>
>> +static int kirin_drm_connectors_register(struct drm_device *dev)
>> +{
>> + struct drm_connector *connector;
>> + struct drm_connector *failed_connector;
>> + i
Hi Jonathan,
Am 29.06.2016 um 19:52 schrieb Jonathan Corbet :
> On Wed, 29 Jun 2016 19:35:46 +0200
> Markus Heiser wrote:
>
>>> I would love it if you would take the flat-table and man-page work,
>>> separate them out, and make them work with the *existing* Sphinx-based
>>> scheme. If you can
After switching DMA attributes to unsigned long it is easier to just
compare the bits.
Signed-off-by: Krzysztof Kozlowski
[for avr32]
Acked-by: Hans-Christian Noren Egtvedt
[for arc]
Acked-by: Vineet Gupta
[for arm64 and dma-iommu]
Acked-by: Robin Murphy
---
Documentation/DMA-API.txt
The dma-mapping core and the implementations do not change the
DMA attributes passed by pointer. Thus the pointer can point to const
data. However the attributes do not have to be a bitfield. Instead
unsigned long will do fine:
1. This is just simpler. Both in terms of reading the code and sett
Hi,
This is fifth approach for replacing struct dma_attrs with unsigned
long.
The main patch (1/44) doing the change is split into many subpatches
for easier review (2-42). They should be squashed together when
applying.
Rebased on v4.7-rc5.
For easier testing the patchset is available here:
36 matches
Mail list logo
