qemu-ppc
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-ppc] [QEMU-PPC] [PATCH V4 07/11] target/ppc: Don't gen an SDR1


From: Balbir Singh
Subject: Re: [Qemu-ppc] [QEMU-PPC] [PATCH V4 07/11] target/ppc: Don't gen an SDR1 on POWER9 and rework register creation
Date: Mon, 27 Feb 2017 15:06:34 +1100
User-agent: Mutt/1.7.1 (2016-10-04)

On Fri, Feb 24, 2017 at 12:05:13PM +1100, Suraj Jitindar Singh wrote:
> POWER9 doesn't have a storage description register 1 (SDR1) which is used
> to store the base and size of the hash table. Thus we don't need to
> generate this register on the POWER9 cpu model. While we're here, the
> register generation code for 970, POWER5+, POWER<7/8/9> in general is a
> mess where we call a generic function from a model specific function which
> then attempts to call model specific functions, so rework this for
> readability.
> 
> We update ppc_cpu_dump_state so that "info registers" will only display
> the value of sdr1 if the register has been generated.
> 
> As mentioned above the register generation for the pcc->init_proc
> function for 970, POWER5+, POWER7, POWER8 and POWER9 has been reworked
> for improved clarity. Instead of calling init_proc_book3s_64 which then
> attempts to generate the correct registers through a mess of if statements,
> we remove this function and instead call the appropriate register
> generation functions directly. This follows the register generation model
> used for earlier cpu models (pre-970) whereby cpu specific registers are
> generated directly in the init_proc function and makes it easier to
> add/remove specific registers for new cpu models.
>

Honestly I prefer less code duplication and I don't think the parsing of
the generation based on model numbers is complex. The problem with duplication
is it almost always leads to BUGS

Balbir Singh. 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]