Displaying 14 results from an estimated 14 matches for "monolitically".
Did you mean:
monolithically
2015 Nov 10
2
[PATCH v3 0/3] virtio DMA API core stuff
On Sun, Nov 08, 2015 at 12:49:46PM +0100, Joerg Roedel wrote:
> On Sun, Nov 08, 2015 at 12:37:47PM +0200, Michael S. Tsirkin wrote:
> > I have no problem with that. For example, can we teach
> > the DMA API on intel x86 to use PT for virtio by default?
> > That would allow merging Andy's patches with
> > full compatibility with old guests and hosts.
>
> Well,
2015 Nov 10
2
[PATCH v3 0/3] virtio DMA API core stuff
On Sun, Nov 08, 2015 at 12:49:46PM +0100, Joerg Roedel wrote:
> On Sun, Nov 08, 2015 at 12:37:47PM +0200, Michael S. Tsirkin wrote:
> > I have no problem with that. For example, can we teach
> > the DMA API on intel x86 to use PT for virtio by default?
> > That would allow merging Andy's patches with
> > full compatibility with old guests and hosts.
>
> Well,
2006 Mar 20
5
Merge strategy for klibc
...e arch-specific code for i386
and x86-64; other architectures are going to need some minor cleanup in
setup.c or the equvalent.
The current git tree includes a number of utilities, like dash (sh),
which aren't used by the default kinit configuration. Additionally,
right now kinit is built monolitically, in other words there isn't a
CONFIG_ option to turn off nfsmount, for example.
Again, I'm more than willing to put the tree in any particular state
that makes sense.
3. Path: it probably would make sense to push this into -mm first?
It's taken this long, I'd like to make thi...
2015 Nov 10
0
[PATCH v3 0/3] virtio DMA API core stuff
On Nov 10, 2015 7:02 AM, "Michael S. Tsirkin" <mst at redhat.com> wrote:
>
> On Sun, Nov 08, 2015 at 12:49:46PM +0100, Joerg Roedel wrote:
> > On Sun, Nov 08, 2015 at 12:37:47PM +0200, Michael S. Tsirkin wrote:
> > > I have no problem with that. For example, can we teach
> > > the DMA API on intel x86 to use PT for virtio by default?
> > >
2015 Nov 11
2
[PATCH v3 0/3] virtio DMA API core stuff
On Tue, Nov 10, 2015 at 10:54:21AM -0800, Andy Lutomirski wrote:
> On Nov 10, 2015 7:02 AM, "Michael S. Tsirkin" <mst at redhat.com> wrote:
> >
> > On Sun, Nov 08, 2015 at 12:49:46PM +0100, Joerg Roedel wrote:
> > > On Sun, Nov 08, 2015 at 12:37:47PM +0200, Michael S. Tsirkin wrote:
> > > > I have no problem with that. For example, can we teach
2015 Nov 11
2
[PATCH v3 0/3] virtio DMA API core stuff
On Tue, Nov 10, 2015 at 10:54:21AM -0800, Andy Lutomirski wrote:
> On Nov 10, 2015 7:02 AM, "Michael S. Tsirkin" <mst at redhat.com> wrote:
> >
> > On Sun, Nov 08, 2015 at 12:49:46PM +0100, Joerg Roedel wrote:
> > > On Sun, Nov 08, 2015 at 12:37:47PM +0200, Michael S. Tsirkin wrote:
> > > > I have no problem with that. For example, can we teach
2015 Oct 28
2
[PATCH v3 0/3] virtio DMA API core stuff
On Wed, Oct 28, 2015 at 10:35:27PM +0900, David Woodhouse wrote:
> On Wed, 2015-10-28 at 13:35 +0200, Michael S. Tsirkin wrote:
> > E.g. on intel x86, there's an option iommu=pt which does the 1:1
> > thing for devices when used by kernel, but enables
> > the iommu if used by userspace/VMs.
>
> That's none of your business.
>
> You call the DMA API when
2015 Oct 28
2
[PATCH v3 0/3] virtio DMA API core stuff
On Wed, Oct 28, 2015 at 10:35:27PM +0900, David Woodhouse wrote:
> On Wed, 2015-10-28 at 13:35 +0200, Michael S. Tsirkin wrote:
> > E.g. on intel x86, there's an option iommu=pt which does the 1:1
> > thing for devices when used by kernel, but enables
> > the iommu if used by userspace/VMs.
>
> That's none of your business.
>
> You call the DMA API when
2015 Oct 28
2
[PATCH v3 0/3] virtio DMA API core stuff
On Wed, Oct 28, 2015 at 05:09:47PM +0900, David Woodhouse wrote:
> On Wed, 2015-10-28 at 16:40 +0900, Christian Borntraeger wrote:
> > Am 28.10.2015 um 16:17 schrieb Michael S. Tsirkin:
> > > On Tue, Oct 27, 2015 at 11:38:57PM -0700, Andy Lutomirski wrote:
> > > > This switches virtio to use the DMA API unconditionally. I'm sure
> > > > it breaks
2015 Oct 28
2
[PATCH v3 0/3] virtio DMA API core stuff
On Wed, Oct 28, 2015 at 05:09:47PM +0900, David Woodhouse wrote:
> On Wed, 2015-10-28 at 16:40 +0900, Christian Borntraeger wrote:
> > Am 28.10.2015 um 16:17 schrieb Michael S. Tsirkin:
> > > On Tue, Oct 27, 2015 at 11:38:57PM -0700, Andy Lutomirski wrote:
> > > > This switches virtio to use the DMA API unconditionally. I'm sure
> > > > it breaks
2015 Nov 11
0
[PATCH v3 0/3] virtio DMA API core stuff
On Wed, Nov 11, 2015 at 2:05 AM, Michael S. Tsirkin <mst at redhat.com> wrote:
> On Tue, Nov 10, 2015 at 10:54:21AM -0800, Andy Lutomirski wrote:
>> On Nov 10, 2015 7:02 AM, "Michael S. Tsirkin" <mst at redhat.com> wrote:
>> >
>> > On Sun, Nov 08, 2015 at 12:49:46PM +0100, Joerg Roedel wrote:
>> > > On Sun, Nov 08, 2015 at 12:37:47PM
2015 Nov 08
3
[PATCH v3 0/3] virtio DMA API core stuff
On Thu, Oct 29, 2015 at 05:18:56PM +0100, David Woodhouse wrote:
> On Thu, 2015-10-29 at 11:01 +0200, Michael S. Tsirkin wrote:
> >
> > Example: you have a mix of assigned devices and virtio devices. You
> > don't trust your assigned device vendor not to corrupt your memory so
> > you want to limit the damage your assigned device can do to your
> > guest,
>
2015 Nov 08
3
[PATCH v3 0/3] virtio DMA API core stuff
On Thu, Oct 29, 2015 at 05:18:56PM +0100, David Woodhouse wrote:
> On Thu, 2015-10-29 at 11:01 +0200, Michael S. Tsirkin wrote:
> >
> > Example: you have a mix of assigned devices and virtio devices. You
> > don't trust your assigned device vendor not to corrupt your memory so
> > you want to limit the damage your assigned device can do to your
> > guest,
>
2016 Jul 21
3
[RFC] One or many git repositories?
On Wed, Jul 20, 2016 at 6:18 PM, Renato Golin <renato.golin at linaro.org>
wrote:
> On 21 July 2016 at 02:06, Daniel Berlin <dberlin at dberlin.org> wrote:
> >> Checking out all of it is bad,
> >
> > Define bad?
> > Time?
> > Disk space?
> > Bandwidth?
> >
> > I mean, we already assume you have a lot of each anyway?
>
> This