On 15/12/11 12:37, Alexander Graf wrote:
>
> On 15.12.2011, at 02:27, Matt Evans wrote:
>
>> Heya Alex,
>>
>> On 13/12/11 19:23, Alexander Graf wrote:
>>>
>>> On 13.12.2011, at 08:00, Matt Evans wrote:
>>>
This patch adds a new arch directory, powerpc, basic file structure,
register
>
On 15.12.2011, at 02:27, Matt Evans wrote:
> Heya Alex,
>
> On 13/12/11 19:23, Alexander Graf wrote:
>>
>> On 13.12.2011, at 08:00, Matt Evans wrote:
>>
>>> This patch adds a new arch directory, powerpc, basic file structure,
>>> register
>>> setup and where necessary stubs out arch-specific
Heya Alex,
On 13/12/11 19:23, Alexander Graf wrote:
>
> On 13.12.2011, at 08:00, Matt Evans wrote:
>
>> This patch adds a new arch directory, powerpc, basic file structure, register
>> setup and where necessary stubs out arch-specific functions (e.g. interrupts,
>> runloop exits) that later pat
On 12/14/2011 06:50 PM, Alexander Graf wrote:
>
> On 14.12.2011, at 11:41, Benjamin Herrenschmidt wrote:
>
>> On Wed, 2011-12-14 at 12:30 +0200, Pekka Enberg wrote:
>>> Sure, I actually already applied this patch earlier today. I'd still
>>> be interested in pointers to relevant documentation bec
On Wed, 14 Dec 2011, Alexander Graf wrote:
The MMU isn't that hard to grasp. I would've said take a look at my
presentation from 2010:
http://www.linux-kvm.org/page/KVM_Forum_2010
but the video seems to have been removed since :(
Damn. Who could we ping to get them back up?
On Wed, 2011-12-14 at 12:30 +0200, Pekka Enberg wrote:
> Sure, I actually already applied this patch earlier today. I'd still
> be interested in pointers to relevant documentation because I'd love
> to have some understanding of the PPC architecture code.
The architecture documents are on power.o
On Wed, Dec 14, 2011 at 11:38 AM, Benjamin Herrenschmidt
wrote:
>> This looks nice and clean - but I don't really know PPC! Would you be
>> able to point me to some relevant documentation? Are there other PPC
>> folks out there that would be interested in taking a look at these
>> patches?
>
> I c
> This looks nice and clean - but I don't really know PPC! Would you be
> able to point me to some relevant documentation? Are there other PPC
> folks out there that would be interested in taking a look at these
> patches?
I can try to spend time having a look but I'd rather just trust Matt :-)
A
On 14 Dec 2011, at 04:43, Pekka Enberg wrote:
> On Tue, Dec 13, 2011 at 9:00 AM, Matt Evans wrote:
>> +int irq__register_device(u32 dev, u8 *num, u8 *pin, u8 *line)
>> +{
>> + fprintf(stderr, "irq__register_device(%d, [%d], [%d], [%d]\n",
>> + dev, *num, *pin, *line);
>> +
On Tue, Dec 13, 2011 at 9:00 AM, Matt Evans wrote:
> +int irq__register_device(u32 dev, u8 *num, u8 *pin, u8 *line)
> +{
> + fprintf(stderr, "irq__register_device(%d, [%d], [%d], [%d]\n",
> + dev, *num, *pin, *line);
> + return 0;
> +}
> +
> +void irq__init(struct kvm *kv
On 13.12.2011, at 08:00, Matt Evans wrote:
> This patch adds a new arch directory, powerpc, basic file structure, register
> setup and where necessary stubs out arch-specific functions (e.g. interrupts,
> runloop exits) that later patches will provide. The target is an
> SPAPR-compliant PPC64 m
On Tue, Dec 13, 2011 at 9:00 AM, Matt Evans wrote:
> This patch adds a new arch directory, powerpc, basic file structure, register
> setup and where necessary stubs out arch-specific functions (e.g. interrupts,
> runloop exits) that later patches will provide. The target is an
> SPAPR-compliant P
This patch adds a new arch directory, powerpc, basic file structure, register
setup and where necessary stubs out arch-specific functions (e.g. interrupts,
runloop exits) that later patches will provide. The target is an
SPAPR-compliant PPC64 machine (i.e. pSeries); there is no support for PPC32 o
13 matches
Mail list logo
